lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2765) Shard/Node states
Date Thu, 06 Oct 2011 23:33:29 GMT


Mark Miller commented on SOLR-2765:
----------------------------------- 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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message