lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Dunning (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2765) Shard/Node states
Date Tue, 11 Oct 2011 12:21:12 GMT


Ted Dunning commented on SOLR-2765:

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.
Are these truly defunct?  Or just not used yet?

If the latter, I would keep them.

I don't think that handling all watches is a problem at this point given that >1000 node
search clusters probably don't exist.

> 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