[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160946#comment-13160946
]
Sami Siren commented on SOLR-2880:
----------------------------------
bq. Would it be more convenient to store whats on the nodes in node_states and
node_assigments as human readable
I agree, I'll change that.
bq. I actually just noticed we use the same ZKNodeProps for the current leader
zk node as we use for the node in the cluster state
- not a problem for info that doesn't change, but now that we store the
"active,replicating" state there, as well as other properties that could be
dynamic, it ends up with stale data as those properties change.
Who uses the information from the leader node (what is actually needed there?)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
