[
https://issues.apache.org/jira/browse/SOLR-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637362#comment-16637362
]
ASF subversion and git services commented on SOLR-12815:
--------------------------------------------------------
Commit ba35bd54b4512240066e4e75f1e598a979e5b5ec in lucene-solr's branch
refs/heads/branch_7x from Andrzej Bialecki
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ba35bd5 ]
SOLR-12815: Implement maxOps limit for IndexSizeTrigger.
> Implement maxOps limit for IndexSizeTrigger
> -------------------------------------------
>
> Key: SOLR-12815
> URL: https://issues.apache.org/jira/browse/SOLR-12815
> 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
>
> {{IndexSizeTrigger}} can currently generate unlimited number of requested
> operations (such as split shard). Combined with the avalanche effect in
> SOLR-12730 this may cause a massive spike in the cluster load, and some of
> these operations may fail.
> It's probably better to put an arbitrary limit on the maximum number of
> generated ops requested in one trigger event. This will delay some of the
> needed changes (thus leading to thresholds being exceeded to a larger degree)
> but it will increase the likelihood that all operations succeed.
> A similar limit already exists in {{SearchRateTrigger}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
