[jira] [Updated] (SOLR-12815) Implement maxOps limit for IndexSizeTrigger

["Andrzej Bialecki (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrzej Bialecki updated SOLR-12815:
------------------------------------
    Fix Version/s: 7.6

> Implement maxOps limit for IndexSizeTrigger
> -------------------------------------------
>
>                 Key: SOLR-12815
>                 URL: https://issues.apache.org/jira/browse/SOLR-12815
>             Project: Solr
>          Issue Type: Sub-task
>          Components: AutoScaling
>            Reporter: Andrzej Bialecki
>            Assignee: Andrzej Bialecki
>            Priority: Major
>             Fix For: 7.6
>
>
> {{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
(v8.3.4#803005)

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