[
https://issues.apache.org/jira/browse/SOLR-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859176#comment-16859176
]
Andrzej Bialecki commented on SOLR-13530:
------------------------------------------
I understand that the scope of this issue is somewhat different, but there's an
already existing mechanism which may be used to mitigate such situations before
they happen - {{IndexSizeTrigger}} can automatically execute {{SPLITSHARD}}
when a replica grows beyond a specified threshold, expressed either as a number
of bytes or a number of docs.
> Control requests to Solr based on the core size
> -----------------------------------------------
>
> Key: SOLR-13530
> URL: https://issues.apache.org/jira/browse/SOLR-13530
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Anshum Gupta
> Priority: Major
>
> Large cores are almost always problematic. They show up as increased
> replication times, recovery times, and much more. They also often are
> attempted to be handled by using a larger heap, which is also almost always
> an even bigger problem.
> We should be able to reject requests or at least log/notify when Solr core
> grows beyond a specific threshold.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
