[
https://issues.apache.org/jira/browse/SOLR-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828021#comment-13828021
]
Mark Miller commented on SOLR-5436:
-----------------------------------
Ah, right - good point. We don't catch the watcher connection event and have
peek fail.
The latest change should handle this case though. Either the connection to ZK
is gone and the peek call will fail when it retries after getting the
connection watcher event. Or the connection might have failed and come back
before the retry tries to talk to zk - in this case, the code change I just
made should kill the current Overseer threads - either when we are alerted the
Overseer has changed or when we start a new overseer because the zk connection
was expired.
> Eliminate the 1500ms wait in overseer loop
> ------------------------------------------
>
> Key: SOLR-5436
> URL: https://issues.apache.org/jira/browse/SOLR-5436
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Minor
> Attachments: SOLR-5436.patch, SOLR-5436.patch, SOLR-5436.patch,
> SOLR-5436.patch, SOLR-5436.patch, SOLR-5436.patch
>
>
> The Overseer thread waits 1500 ms before it polls for new events. The wait
> should be eliminated and it should just wait for new events till they come
> the way it is done in OverseerCollectionProcessor
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
