hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dustin Cote (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3924) Submitting an application to standby ResourceManager should respond better than Connection Refused
Date Tue, 14 Jul 2015 19:05:05 GMT

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

Dustin Cote commented on YARN-3924:
-----------------------------------

It doesn't if you put in the standby resource manager for the 'jobTracker' stanza in oozie
or if you misconfigure yarn.resourcemanager.ha.rm-ids to include only the standby resource
manager.  The oozie scenario is more the real user scenario, but I reproduced this by using
the yarn.resourcemanager.ha.rm-ids method.  I assume closing the 8032 port for the standby
RM is by design, but can we indicate that the RM is in standby instead of just saying connection
refused?  

> 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
>            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