lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-8973) TX-frenzy on Zookeeper when collection is put to use
Date Mon, 09 May 2016 22:53:12 GMT


Hoss Man updated SOLR-8973:
    Fix Version/s:     (was: 6.0)
                   master (7.0)

Manually correcting fixVersion per Step #S5 of LUCENE-7271

> TX-frenzy on Zookeeper when collection is put to use
> ----------------------------------------------------
>                 Key: SOLR-8973
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 6.0
>            Reporter: Janmejay Singh
>            Assignee: Scott Blum
>              Labels: collections, patch-available, solrcloud, zookeeper
>             Fix For: 5.5.1, 5.6, 6.1, master (7.0)
>         Attachments: SOLR-8973-ZkStateReader.patch, SOLR-8973.patch, SOLR-8973.patch,
> This is to do with a distributed data-race. Core-creation happens at a time when collection
is not yet visible to the node. In this case a fallback code-path is used which de-references
collection-state lazily (on demand) as opposed to setting a watch and keeping it cached locally.
> Due to this, as requests towards the core mount, it generates ZK fetch for collection
proportionately. On a large solr-cloud cluster, this generates several Gbps of TX traffic
on ZK nodes. This affects indexing throughput(which floors) in addition to running ZK node
out of network bandwidth. 
> On smaller solr-cloud clusters its hard to run into, because probability of this race
materializing reduces.

This message was sent by Atlassian JIRA

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

View raw message