lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2358) Distributing Indexing
Date Fri, 07 Oct 2011 21:04:30 GMT


Yonik Seeley commented on SOLR-2358:

As far as locking vs leader, I think maybe both can make sense.
Some things are logically more node specific and a lock can make more sense there (so that
a node can modify it's own state).
Also, something like a command to create a new collection might be easier with a cluster lock.
 The node that received the command can just do it, rather than introducing logic to forward
the command to the cluster leader (or put the request in a ZK queue or something, to be pulled
by someone, which still needs coordination to make sure only one node is trying to do it).

On the other hand, cluster overseer code that might want to watch the cluster and change the
configuration... a single cluster leader makes sense there (and they may end up also grabbing
some sort of lock to avoid conflicts with what other nodes may do).
> Distributing Indexing
> ---------------------
>                 Key: SOLR-2358
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud, update
>            Reporter: William Mayor
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: SOLR-2358.patch
> The first steps towards creating distributed indexing functionality in Solr

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message