hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3924) Submitting an application to standby ResourceManager should respond better than Connection Refused
Date Sat, 15 Aug 2015 07:34:46 GMT

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

Karthik Kambatla commented on YARN-3924:
----------------------------------------

bq. not somehow making clear about two cases of (RMs being down,client config problems etc)
vs (RMs in standby).

Fair point. I would like to understand what the user/admin would do differently in the two
cases. Seeing the proposed message, the admin would likely go through all the RMs specified
in the config and check their HA state. If it is a config issue, the admin should realize
it straight-away. If the RM is down or in standby, the admin would likely do the needful to
get it to active. I see the value in making this simpler for the admin, but the config issue
is likely a one-time thing. Augmenting ClientRMService and other user-visible services to
have an Active/Standby mode is rather involved, and I want to make sure the usability improvement
is worth the effort and risk. 

> Submitting an application to standby ResourceManager should respond better than Connection
Refused
> --------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3924
>                 URL: https://issues.apache.org/jira/browse/YARN-3924
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>            Reporter: Dustin Cote
>            Assignee: Ajith S
>            Priority: Minor
>
> When submitting an application directly to a standby resource manager, the resource manager
responds with 'Connection Refused' rather than indicating that it is a standby resource manager.
 Because the resource manager is aware of its own state, I feel like we can have the 8032
port open for standby resource managers and reject the request with something like 'Cannot
process application submission from this standby resource manager'.  
> This would be especially helpful for debugging oozie problems when users put in the wrong
address for the 'jobtracker' (i.e. they don't put the logical RM address but rather point
to a specific resource manager).  



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

Mime
View raw message