lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] [Commented] (SOLR-11714) AddReplicaSuggester endless loop
Date Tue, 09 Jan 2018 15:32:01 GMT


Andrzej Bialecki  commented on SOLR-11714:

After discussing this with Noble it seems that the best way to solve this is to allow some
triggers to calculate the list of expected changes (eg. a list of COLL_SHARD replicas to add),
and then explicitly iterate in {{ComputePlanAction}} as many times as needed to consume the
list of these changes, and initializing suggesters with one change at a time (which would
eventually result in calculating up to the same number of ops, though some of them may be

> AddReplicaSuggester endless loop
> --------------------------------
>                 Key: SOLR-11714
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: AutoScaling
>    Affects Versions: 7.2, master (8.0)
>            Reporter: Andrzej Bialecki 
>            Assignee: Noble Paul
>         Attachments: 7.2-disable-search-rate-trigger.diff, SOLR-11714.diff
> {{SearchRateTrigger}} events are processed by {{ComputePlanAction}} and depending on
the condition either a MoveReplicaSuggester or AddReplicaSuggester is selected.
> When {{AddReplicaSuggester}} is selected there's currently a bug in master, due to an
API change (Hint.COLL_SHARD should be used instead of Hint.COLL). However, after fixing that
bug {{ComputePlanAction}} goes into an endless loop because the suggester endlessly keeps
creating new operations.
> Please see the patch that fixes the Hint.COLL_SHARD issue and modifies the unit test
to illustrate this failure.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message