lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Commented] (SOLR-11423) Overseer queue needs a hard cap (maximum size) that clients respect
Date Thu, 05 Oct 2017 22:32:01 GMT


Noble Paul commented on SOLR-11423:

Waiting can help. If every node errors out immediately after the cut off the items in queue
can get cleared immediately and there will be  starvation . If we wait and retry after sometime
, we can ensure that the events are generated at a lower rate. It helps in cases where a GC
pause caused a pile up. 

> Overseer queue needs a hard cap (maximum size) that clients respect
> -------------------------------------------------------------------
>                 Key: SOLR-11423
>                 URL:
>             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
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message