lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Dunning (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2765) Shard/Node states
Date Fri, 07 Oct 2011 23:17:30 GMT


Ted Dunning commented on SOLR-2765:

There are several kinds of shard state changes.  As I see it, all of them resolve into two
situations.  One is "more replicas are needed" and the other is "fewer replicas are needed".
 In the former case, the overseer will assign one or more nodes additional shards to serve
and the nodes will take it from there, eventually advertising that they handle those shards.
 In the latter case, the overseer will edit the assignments for one or more nodes reducing
their duties.  The nodes will notice that and will close the corresponding indexes.

It is possible that you want to have a loaded-but-not-available-for-searching state for shards.
 In that case, what you really have is two nearly orthogonal specifications, one for the nodes
and the other for the clients.  The node assignments are just as above, but the client specification
determines which nodes the client is allowed to ask for which shards/collections.

Does that answer your question?

> Shard/Node states
> -----------------
>                 Key: SOLR-2765
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>         Attachments: incremental_update.patch, shard-roles.patch
> Need state for shards that indicate they are recovering, active/enabled, or disabled.

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