lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Johnson (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-2765) Shard/Node states
Date Tue, 11 Oct 2011 02:44:29 GMT


Jamie Johnson updated SOLR-2765:

    Attachment: solrcloud.patch

The latest patch fixes the issue I had mentioned before, where live_nodes wasn't properly
getting updated.  This implementation also keeps ClusterState (used to be CloudState) and
Slice immutable.  

The following is a list of things that can still be done:

# Consider removing ZkStateReader.updateCloudState methods, these aren't called by anything
other than tests right now.  On a side note, the current implementation processes every watch
event instead of having the 5s delay.  This could cause some issues performance wise when
the cluster is first coming up since everyone will be trying to write to the cluster state.
 If we have to add that back it should be a really simple change.
# Update the tests to read from /cluster_state instead of /collections
# Decide if ClusterState should be the ideal state or actual (i.e. do we maintain information
in /collections as ideal and update ClusterState to track nodes going down).  Currently ClusterState
is ideal.  This would require some leader to track when a node is no longer live, so should
probably be pushed off.

Any thoughts on these?  Specifically 1.
> Shard/Node states
> -----------------
>                 Key: SOLR-2765
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud, update
>            Reporter: Yonik Seeley
>             Fix For: 4.0
>         Attachments: cluster_state-file.patch, combined.patch, incremental_update.patch,
scheduled_executors.patch, shard-roles.patch, solrcloud.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