[
https://issues.apache.org/jira/browse/SOLR-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011302#comment-14011302
]
Noble Paul edited comment on SOLR-6091 at 5/28/14 4:50 PM:
-----------------------------------------------------------
I have fixed this and I have logged it whenever a race condition occurs. So ,
the logs say that the race condition occurs . But after a few (10+) restarts I
could still end up without an Overseer . SOLR-6095 is another issue I have
identified and fixed it for local testing . So these 2 issues together have
resolved the problem
was (Author: noble.paul):
I have fixed this and I have logged it whenever a race condition occurs. So ,
the logs say that the race condition occurs . But after a few (10+) restarts I
could still end up without an Overseer . SOLR-6095 is another issue I have
identified and fixed it for local testing
> Race condition in prioritizeOverseerNodes can trigger extra QUIT operations
> ---------------------------------------------------------------------------
>
> Key: SOLR-6091
> URL: https://issues.apache.org/jira/browse/SOLR-6091
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.7, 4.8
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-6091.patch
>
>
> When using the overseer roles feature, there is a possibility of more than
> one thread executing the prioritizeOverseerNodes method and extra QUIT
> commands being inserted into the overseer queue.
> At a minimum, the prioritizeOverseerNodes should be synchronized to avoid a
> race condition.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
