[
https://issues.apache.org/jira/browse/HADOOP-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546338#comment-13546338
]
Hadoop QA commented on HADOOP-9183:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12563602/HADOOP-9183.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2000//console
This message is automatically generated.
> Potential deadlock in ActiveStandbyElector
> ------------------------------------------
>
> Key: HADOOP-9183
> URL: https://issues.apache.org/jira/browse/HADOOP-9183
> Project: Hadoop Common
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.0.2-alpha
> Reporter: Tom White
> Assignee: Tom White
> Attachments: 2_jcarder_result_1.png, 3_jcarder_result_0.png,
> HADOOP-9183.patch, HADOOP-9183.patch
>
>
> A jcarder run found a potential deadlock in the locking of
> ActiveStandbyElector and ActiveStandbyElector.WatcherWithClientRef. No
> deadlock has been seen in practice, this is just a theoretical possibility at
> the moment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
