[
https://issues.apache.org/jira/browse/SOLR-11670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379030#comment-16379030
]
Andrzej Bialecki commented on SOLR-11670:
------------------------------------------
Patch containing the following:
* a {{MaintenanceTask}} API that components may use for registering tasks with
Overseer. Tasks are initialized using key / value pairs from
{{/clusterprops.json}}
* {{MaintenanceTasks}} component, which is a registry and runner of tasks.
This component also monitors changes to {{/clusterprops.json}} and
re-initializes tasks and their schedule as needed.
* implementation of {{InactiveSliceCleanupTask}}, which deletes inactive
slices that exceeded a configured TTL time. This task is registered by
{{SplitShardCmd}}.
* changes to {{SplitShardTest}} to exercise this code.
This code is also available on branch {{jira/solr-11670}}.
> Implement a periodic house-keeping task
> ---------------------------------------
>
> Key: SOLR-11670
> URL: https://issues.apache.org/jira/browse/SOLR-11670
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-11670.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
