[
https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806914#comment-13806914
]
Zhijie Shen commented on YARN-674:
----------------------------------
bq. Yes I have removed the error purposefully..here are the thoughts.
parseCredentials is not asynchronous, right? Therefore, is it better to fail
the application submission immediately instead of forcing the client the come
back to check the status? In fact, in submitApplication, there're already
several points where the application submission can fail immediately, even
though the application START is handled asynchronously.
bq. Not understanding how to fix that findbug warning .. should I add that too
into exclude-findbug.xml? I tried this. Even eclipse doesn't complain
Maybe you can do
{code}
if (event instanceof DelegationTokenRenewerAppSubmitEvent) {
...
}
{code}
to avoid the findbug warning?
> Slow or failing DelegationToken renewals on submission itself make RM
> unavailable
> ---------------------------------------------------------------------------------
>
> Key: YARN-674
> URL: https://issues.apache.org/jira/browse/YARN-674
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Omkar Vinit Joshi
> Attachments: YARN-674.1.patch, YARN-674.2.patch
>
>
> This was caused by YARN-280. A slow or a down NameNode for will make it look
> like RM is unavailable as it may run out of RPC handlers due to blocked
> client submissions.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
