[
https://issues.apache.org/jira/browse/SOLR-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004008#comment-14004008
]
Jessica Cheng commented on SOLR-6091:
-------------------------------------
I think that's a good idea, and maybe we can go further and include the id in
the /overseer/leader file (e.g.
91790253334528928-<host>:8983_solr-n_0000000013) so that the Overseer would
only quit if its ID actually matched it completely. It'd be like a CAS--do this
operation only if the state I read to make this decision is still valid.
> 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: Shalin Shekhar Mangar
> 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]
