[
https://issues.apache.org/jira/browse/SOLR-11670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391030#comment-16391030
]
Andrzej Bialecki commented on SOLR-11670:
------------------------------------------
bq. why do we make a copy of triggerListeners in the processor
If we change {{AutoScalingConfig}} while an event is being processed then we
may get inconsistent listener notifications. I noticed this situation in tests
where old events (from a previous test) would continue to be processed during
the next test method, but they produced only some of the notifications one
would normally expect (because the listeners have been cleared between eg.
BEFORE_ACTION and AFTER_ACTION).
Under normal circumstances this shouldn't be a big deal, but in tests this is
much more likely to happen.
> 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, SOLR-11670.patch, 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
