[
https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662694#comment-13662694
]
Jian He commented on YARN-513:
------------------------------
Xuan, thanks for your comments.
I did the above tests already. Currently, its able to catch ConnectException,
but not able to catch EOFException which is thrown when the connection is lost,
since EOFException is already wrapped as IOException deep down the RPC layer
see HADOOP-9576. The solution now is to add IOException to the
exceptionToPolicyMap. After HADOOP-9576, we can catch EOFException
I uploaded the latest patch which only adds one line change:
exceptionToPolicyMap.put(IOException.class, retryPolicy);
Enjoy your honey moon~
> Create common proxy client for communicating with RM
> ----------------------------------------------------
>
> Key: YARN-513
> URL: https://issues.apache.org/jira/browse/YARN-513
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Jian He
> Attachments: YARN-513.1.patch, YARN-513.2.patch, YARN-513.3.patch,
> YARN-513.4.patch, YARN.513.5.patch, YARN-513.6.patch, YARN-513.7.patch
>
>
> When the RM is restarting, the NM, AM and Clients should wait for some time
> for the RM to come back up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
