[
https://issues.apache.org/jira/browse/SOLR-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828451#comment-13828451
]
Mark Miller commented on SOLR-5436:
-----------------------------------
bq. better than expecting the consumer of the API to take care of that
It's really an Overseer specific thing though - I don't think it's a problem
for the consumer of the DistributedQueue API. We are dealing with special
Overseer considerations, and I don't really see the strategy for that as a
consumer.
A standard consumer of the queue API does not necessary need to detect this
kind of zk connection flap - It's kind of Overseer specific I think.
Adding may actually hurt the distributedqueue consumer experience - you expect
to keep working the queue in the face of zk connection/disconnection without
any special handling.
> 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, 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]
