[ 
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123357#comment-13123357
 ] 

Mark Miller commented on SOLR-2765:
-----------------------------------

Away for the weekend, and a lot to comment on, but will have to wait.

FYI though:

bq. current implementation on trunk polls the state every 5 seconds for updates 
instead of using watchers.

I don't think so? It's been some time since I did this, but it should be using 
a watcher - the 5 seconds is just how long it should wait before actually 
grabbing the state - the idea being if node after node comes up and triggers 
the watch, if there is already a state update scheduled (5 seconds after the 
watch is triggered by default), a new update is not asked for - eg if nodes are 
firing up by the hundreds, the state is still only updated once every 5 
seconds. It's still triggered by a watch though - I believe a watch on the 
shards node itself - which a core will ping with a set null data after 
registering in zk. Before adding the incremental update patch, the idea was 
that you could change a sub property on a node, and still trigger a reload of 
the state by triggering the watches on the shards node.
                
> 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: incremental_update.patch, 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to