lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect
Date Fri, 08 Dec 2017 18:38:02 GMT

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

Tomás Fernández Löbbe edited comment on SOLR-11423 at 12/8/17 6:37 PM:
-----------------------------------------------------------------------

bq. Sounds good to me. So backport to branch_7_2 and branch_7x?
+1. And lets fix CHANGES.txt
Is this OK [~jpountz]? This is not a bugfix, but as you said, it's in an odd state right now,
and since it was included in the 7.1 CHANGES I feel we should correct ASAP


was (Author: tomasflobbe):
bq. Sounds good to me. So backport to branch_7_2 and branch_7x?
+1. And lets fix CHANGES.txt

> Overseer queue needs a hard cap (maximum size) that clients respect
> -------------------------------------------------------------------
>
>                 Key: SOLR-11423
>                 URL: https://issues.apache.org/jira/browse/SOLR-11423
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Scott Blum
>            Assignee: Scott Blum
>
> When Solr gets into pathological GC thrashing states, it can fill the overseer queue
with literally thousands and thousands of queued state changes.  Many of these end up being
duplicated up/down state updates.  Our production cluster has gotten to the 100k queued items
level many times, and there's nothing useful you can do at this point except manually purge
the queue in ZK.  Recently, it hit 3 million queued items, at which point our entire ZK cluster
exploded.
> I propose a hard cap.  Any client trying to enqueue a item when a queue is full would
throw an exception.  I was thinking maybe 10,000 items would be a reasonable limit.  Thoughts?



--
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


Mime
View raw message