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 "Vinayakumar B (JIRA)" <ji...@apache.org> on 2015/02/17 10:52:12 UTC
[jira] [Updated] (HADOOP-11000) HAServiceProtocol's health state is
incorrectly transitioned to SERVICE_NOT_RESPONDING
[ https://issues.apache.org/jira/browse/HADOOP-11000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayakumar B updated HADOOP-11000:
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.7.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks Ming Ma for the patch.
Thanks Chris for the patch.
Committed to trunk and branch-2
> 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
> Fix For: 2.7.0
>
> 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)