You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Description
In the current compaction process, delete rowsets must be merged during the base compaction phase. If there are too many delete rowsets, the system must wait for the base compaction to merge them. Since base compaction runs infrequently, an excessive number of delete rowsets can delay compaction, resulting in too many versions waiting for compaction and eventually causing errors.
Solution
Implement a check during every delete operation to verify if the tablet already contains too many delete rowsets.
The threshold for the number of delete rowsets should be configurable via a setting in config.
If the number of delete rowsets exceeds this threshold, return an error to prevent further accumulation.
This solution aims to ensure that the compaction process is performed in a timely manner and prevent excessive versions from causing errors due to delayed compaction.
Search before asking
Description
In the current compaction process, delete rowsets must be merged during the base compaction phase. If there are too many delete rowsets, the system must wait for the base compaction to merge them. Since base compaction runs infrequently, an excessive number of delete rowsets can delay compaction, resulting in too many versions waiting for compaction and eventually causing errors.
Solution
This solution aims to ensure that the compaction process is performed in a timely manner and prevent excessive versions from causing errors due to delayed compaction.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: