[jira] [Commented] (SOLR-11714) AddReplicaSuggester endless loop

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280831#comment-16280831 ] 

ASF subversion and git services commented on SOLR-11714:
--------------------------------------------------------

Commit 034daf424c13b467c16629823bc3b94395c738f3 in lucene-solr's branch refs/heads/branch_7_2 from [~ab]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=034daf4 ]

SOLR-11714: Disable searchRate trigger due to a suggester bug.


> AddReplicaSuggester endless loop
> --------------------------------
>
>                 Key: SOLR-11714
>                 URL: https://issues.apache.org/jira/browse/SOLR-11714
>             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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org