[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123775#comment-13123775
]
Ted Dunning commented on SOLR-2765:
-----------------------------------
{quote}
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.
{quote}
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: https://issues.apache.org/jira/browse/SOLR-2765
> 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, 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
