[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123612#comment-13123612
]
Jamie Johnson commented on SOLR-2765:
-------------------------------------
So if I am understanding this we still have the live_nodes but we'd remove the
information under collections in favor of a single node which stores the cloud
state in some XML format, correct?
The process would then be in ZkController.register that the new solr instance
gets the current state, attempts to add its information to the file and do an
update to that particular version, if the update fails (presumably because
another solr instance has modified the node resulting in a version bump) we'd
simply repeat this.
Would something like this work for the XML format? We could then iterate
through this and update the CloudState locally whenever a change to this has
happened.
<cloudstate>
<collectionstate name="collection1">
<slice name="slice1">
<shard name="shard1">
<props>
<str name="url">http://.…</str>
<str name="node_name">node</str>
<str name="roles">indexer,searcher</str>
</props>
</shard>
</slice>
</collectionstate>
</cloudstate>
If this seems reasonable I will attempt to make this change.
> 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: 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: [email protected]
For additional commands, e-mail: [email protected]
