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

Jim Brennan commented on YARN-10767:
------------------------------------

[~dmmkr], [~BilwaST], I am not familiar with the RM HA code, so it would be 
better to have someone who has worked in this area take a look. 
[~prabhujoseph], [~pbacsko]?

My observations:

I agree with the need for a null check because findActiveRMHAId can return 
null.  In this case though, maybe we just throw an exception.  Maybe 
findActiveRMHAId should actually throw instead of returning null?

I believe findActiveRMHAId is going to contact each RM to see if it is active, 
so won't this have the same time-out issues?  Or is there a different retry 
policy in this case?   Have you tested this solution to verify it resolves the 
problem?

I wonder if using findActiveRMHAId allows us to simplify this?  If we've 
already determined the active rm, do we really need to loop through the others 
if we fail on the one we know to be active?


> Yarn Logs Command retrying on Standby RM for 30 times
> -----------------------------------------------------
>
>                 Key: YARN-10767
>                 URL: https://issues.apache.org/jira/browse/YARN-10767
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: D M Murali Krishna Reddy
>            Assignee: D M Murali Krishna Reddy
>            Priority: Major
>         Attachments: YARN-10767.001.patch
>
>
> When ResourceManager HA is enabled and the first RM is unavailable, on 
> executing "bin/yarn logs -applicationId <appID> -am 1", we get 
> ConnectionException for connecting to the first RM, the ConnectionException 
> Occurs for 30 times before it tries to connect to the second RM.
>  
> This can be optimized by trying to fetch the logs from the Active RM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to