You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2014/05/20 23:19:38 UTC
[jira] [Commented] (SOLR-6091) Race condition in
prioritizeOverseerNodes can trigger extra QUIT operations
[ https://issues.apache.org/jira/browse/SOLR-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003983#comment-14003983 ]
Shalin Shekhar Mangar commented on SOLR-6091:
---------------------------------------------
Would it be a good idea to include the overseer leader node name for which the QUIT message is intended? I imagine that it'd help us catch wrong/extra QUITs and race conditions during 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: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org