[ 
https://issues.apache.org/jira/browse/HADOOP-11000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323994#comment-14323994
 ] 

Hudson commented on HADOOP-11000:
---------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #7124 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/7124/])
HADOOP-11000. HAServiceProtocol's health state is incorrectly transitioned to 
SERVICE_NOT_RESPONDING (Contributed by Ming Ma) (vinayakumarb: rev 
cf4b7f506dd338ecf2ed4c643b6a6a334e070fca)
* hadoop-common-project/hadoop-common/CHANGES.txt
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ha/HealthMonitor.java
* 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ha/TestHealthMonitor.java
* 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ha/DummyHAService.java


> HAServiceProtocol's health state is incorrectly transitioned to 
> SERVICE_NOT_RESPONDING
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11000
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11000
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HADOOP-11000-2.patch, HADOOP-11000.patch
>
>
> When HAServiceProtocol.monitorHealth throws a HealthCheckFailedException, the 
> actual exception from protocol buffer RPC is a RemoteException that wraps the 
> real exception. Thus the state is incorrectly transitioned to 
> SERVICE_NOT_RESPONDING
> {noformat}
> HealthMonitor.java
> doHealthChecks
>       try {
>         status = proxy.getServiceStatus();
>         proxy.monitorHealth();
>         healthy = true;
>       } catch (HealthCheckFailedException e) {
>         .....
>         enterState(State.SERVICE_UNHEALTHY);
>       } catch (Throwable t) {
>         .....
>         enterState(State.SERVICE_NOT_RESPONDING);
>         .....
>       }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to