[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162811#comment-13162811
]
Sami Siren commented on SOLR-2880:
----------------------------------
bq. Why does the overseer class have it's own cloud state and watches on live
nodes and stuff?
The watch for live nodes is also used for adding watches for node states: when
a new node pops up a watch is generated for /node_states/<node-name>
bq. The ZkControllers ZkStateReader is already tracking all this stuff and
should be the owner of the cloud state, shouldn't it?
Yeah, makes sense. I'll see how that would work.
> Investigate adding an overseer that can assign shards, later do re-balancing,
> etc
> ---------------------------------------------------------------------------------
>
> Key: SOLR-2880
> URL: https://issues.apache.org/jira/browse/SOLR-2880
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0
>
> Attachments: SOLR-2880-merge-elections.patch, SOLR-2880.patch
>
>
--
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]
