You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/12 12:39:11 UTC
[jira] [Closed] (SLING-2885) Race condition in
VotingHandler.promote()
[ https://issues.apache.org/jira/browse/SLING-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli closed SLING-2885.
------------------------------
> Race condition in VotingHandler.promote()
> -----------------------------------------
>
> Key: SLING-2885
> URL: https://issues.apache.org/jira/browse/SLING-2885
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Discovery Impl 1.0.0
> Environment: Discovery Impl version: 0.1.0.R1484784
> Reporter: Marcel Reutegger
> Assignee: Stefan Egli
> Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
> Attachments: error.log
>
>
> Sometimes on initial startup of Sling Discovery it happens that two threads try to promote the same winning vote at the same time. This leads to a failed commit in the repository. The system seems to be OK after the exception. There is an established view and the (single) cluster node is the leader.
> Please note, this is running on Jackrabbit Oak, but might also happen on Jackrabbit 2.x because the basic issue is two sessions trying to add the same child node.
> See attached log excerpt for more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)