[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122409#comment-13122409
]
Mark Miller commented on SOLR-2765:
-----------------------------------
hmmm...you know forever I have been trying to avoid juggling potentially 100's
to 1000's of watchers per node like that. Perhaps it really is the lesser of
all evils though? This whole situation is why I initially avoided incremental
update and it only went in recently. How many zk nodes do you tend to see in
that project with lots of watchers?
The problem with live nodes is that its per solr instance, and some of this
info will probably want to be per core? if we made a new structure that put
cores/shards under a solr instance node, I guess that could reduce the number
watches needed - but I wonder if it's worth the effort - I'd almost rather see
the full watcher option on the current node structure fall down first...
> 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: 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
