lucene-dev mailing list archives

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


Jamie Johnson commented on SOLR-2765:

Yeah 100% agree.  The current implementation of update doesn't check to see if the data in
the node changed, you'd need a watcher on each node to do that.  The other project that I'm
working on does just that.  We create a watcher on /live_nodes to track the list of available
servers, we create a watch on the collection to see if a slice was added/removed, we create
a watcher on each slice (not sure if that is the correct terminology) to check if a shard
is added/removed and subsequently a watcher on each shard to track data changes.  So lots
of watchers all around.  

Would it be easier to store this information on the ephemeral nodes (under live_nodes)?  Then
we only need a watcher for live_nodes (add/remove) and a watcher for each shard under live_nodes
to see if their data changed.  I'm not sure what else is using the collection hierarchy (just
query?), but perhaps would be a bit simpler.

> 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