[
https://issues.apache.org/jira/browse/SOLR-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4073.
-------------------------------
Resolution: Duplicate
Fix Version/s: (was: 4.6)
> Overseer will miss operations in some cases for OverseerCollectionProcessor
> ----------------------------------------------------------------------------
>
> Key: SOLR-4073
> URL: https://issues.apache.org/jira/browse/SOLR-4073
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0, 4.1, 4.2
> Environment: Solr cloud
> Reporter: Raintung Li
> Assignee: Mark Miller
> Attachments: patch-4073
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> One overseer disconnect with Zookeeper, but overseer thread still handle the
> request(A) in the DistributedQueue. Example: overseer thread reconnect
> Zookeeper try to remove the Top's request. "workQueue.remove();".
> Now the other server will take over the overseer privilege because old
> overseer disconnect. Start overseer thread and handle the queue request(A)
> again, and remove the request(A) from queue, then try to get the top's
> request(B, doesn't get). In the this time old overseer reconnect with
> ZooKeeper, and remove the top's request from queue. Now the top request is B,
> it is moved by old overseer server. New overseer server never do B
> request,because this request deleted by old overseer server, at the last this
> request(B) miss operations.
> At best, distributeQueue.peek can get the request's ID that will be removed
> for workqueue.remove(ID), not remove the top's request.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
