Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Some high-impact cluster changes (such as split shard) leave the original data and original state that is no longer actively used. This makes sense due to safety reasons and to make it easier to roll-back the changes.
However, this unused data will accumulate over time, especially when actions like split shard are invoked automatically by the autoscaling framework. We need a periodic task that would clean up this kind of data after a certain period.