lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-12815) Implement maxOps limit for IndexSizeTrigger
Date Thu, 17 Jan 2019 03:15:00 GMT

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

Cassandra Targett commented on SOLR-12815:
------------------------------------------

[~ab], this appears in CHANGES.txt for 7.6, can it be resolved?

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message