You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2014/01/07 03:13:50 UTC
[jira] [Commented] (HADOOP-10209) Fix findbugs in
ActiveStandbyElector
[ https://issues.apache.org/jira/browse/HADOOP-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863821#comment-13863821 ]
Karthik Kambatla commented on HADOOP-10209:
-------------------------------------------
{noformat}
Code Warning
IS Inconsistent synchronization of org.apache.hadoop.ha.ActiveStandbyElector.wantToBeInElection; locked 90% of time
IS Inconsistent synchronization of org.apache.hadoop.ha.ActiveStandbyElector.watcher; locked 85% of time
IS Inconsistent synchronization of org.apache.hadoop.ha.ActiveStandbyElector.zkClient; locked 80% of time
IS Inconsistent synchronization of org.apache.hadoop.ha.ActiveStandbyElector.zkConnectionState; locked 85% of time
{noformat}
> Fix findbugs in ActiveStandbyElector
> ------------------------------------
>
> Key: HADOOP-10209
> URL: https://issues.apache.org/jira/browse/HADOOP-10209
> Project: Hadoop Common
> Issue Type: Bug
> Components: auto-failover
> Affects Versions: 2.2.0
> Reporter: Karthik Kambatla
>
> findBugs points out some multithreaded correctness warnings in ActiveStandbyElector. We should verify and fix those.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)