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 Sun, 09 Oct 2011 20:27:30 GMT


Ted Dunning commented on SOLR-2765:

So in my mind I am not sure why we need the /collections instance anymore. If we maintain
the state of the cluster in /cloudstate but don't remove the nodes that have gone down (as
Mark mentioned) and just update their status, it seems like we should be able to do what we
want. Now admittedly I have not gone through Ted's comment in detail so perhaps there is a
nugget in there that I am missing.
In a sound byte, collections is aspirational and cloudstate is actual.  Collections specifies
what we want to be true and cloudstate tells us what is true at this moment.
> Shard/Node states
> -----------------
>                 Key: SOLR-2765
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>         Attachments: combined.patch, incremental_update.patch, scheduled_executors.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