hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masatake Iwasaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3860) rmadmin -transitionToActive should check the state of non-target node
Date Tue, 30 Jun 2015 04:48:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14607196#comment-14607196

Masatake Iwasaki commented on YARN-3860:

bq. I wonder if this affects the latency of transitioning active by any significant amount?

I think the time to check state of other nodes is small and not to be problem especially when
user is doing manual transition. getServiceState is expected to return or fail immediately
if the node is down. I'll check corner cases but it is a bug if getServiceState blocks long

> rmadmin -transitionToActive should check the state of non-target node
> ---------------------------------------------------------------------
>                 Key: YARN-3860
>                 URL: https://issues.apache.org/jira/browse/YARN-3860
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Masatake Iwasaki
>            Assignee: Masatake Iwasaki
>             Fix For: 2.8.0
>         Attachments: YARN-3860.001.patch, YARN-3860.002.patch, YARN-3860.003.patch
> Users can make both ResouceManagers active by {{rmadmin -transitionToActive}} even if
{{\--forceactive}} option is not given. {{haadmin -transitionToActive}} of HDFS checks whether
non-target nodes are already active but {{rmadmin -transitionToActive}} does not do.

This message was sent by Atlassian JIRA

View raw message