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

Ajith S commented on YARN-3924:
-------------------------------

Hi [~kasha] and [~rohithsharma]

Thank you for inputs guys. The message *None of the RMs specified by ha-ids 
appear to be active.* is fine, but again, as me and [~cote] previously 
mentioned, this is not somehow making clear about two cases of (RMs being 
down,client config problems etc) vs (RMs in standby). I agree that in current 
design its hard to say this as rpc servers are started only if RMs are active. 
So if i could suggest, we can change this so that in case of RMs in standby, 
rpc servers are up and throw standby exception to client.?

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

Reply via email to