[
https://issues.apache.org/jira/browse/HADOOP-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549506#comment-13549506
]
Hudson commented on HADOOP-9183:
--------------------------------
Integrated in Hadoop-trunk-Commit #3212 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3212/])
HADOOP-9183. Potential deadlock in ActiveStandbyElector. (Revision 1431251)
Result = SUCCESS
tomwhite :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1431251
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ha/ActiveStandbyElector.java
> 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
> Fix For: 2.0.3-alpha
>
> Attachments: 2_jcarder_result_1.png, 3_jcarder_result_0.png,
> HADOOP-9183.patch, 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
