You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bob.zhao (JIRA)" <ji...@apache.org> on 2016/08/08 13:45:20 UTC
[jira] [Updated] (YARN-5484) YARN client will still retry for many
times on failover even though RM server throw AccessControlException
[ https://issues.apache.org/jira/browse/YARN-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob.zhao updated YARN-5484:
---------------------------
Description:
1. Enable yarn.acl.enable
2. Set up some queue for users on yarn, for example queue1 only for user1
3. Using user1 to submit app to queue1, it can run successfully.
4. Change user2 to submit app to queue1, it will not be permit submit to queue1.
So, At RM server side, it will throw IOException(ClientRMService.java#submitApplication), which is the parent implementation of the AccessControlException(RMAppManager.java#createAndPopulateNewRMApp), this IOException will be threw to client that cause yarn client frequently failover for many times.
We'b better avoid this behavior that if client got permission deny from server, it should try once and exit, no need to retry.
This issue was introduced by YARN-4522.
was:
1. Enable yarn.acl.enable
2. Set up some queue for users on yarn, for example queue1 onle for user1
3. Using user1 to submit app to queue1, it can run successfully.
4. Change user2 to submit app to queue1, it will not be permit submit to queue1.
So, At RM server side, it will throw IOException(ClientRMService.java#submitApplication), which is the parent implementation of the AccessControlException(RMAppManager.java#createAndPopulateNewRMApp), this IOException will be threw to client that cause yarn client frequently failover for many times.
We'b better avoid this behavior that if client got permission deny from server, it should try once and exit, no need to retry.
This issue was introduced by YARN-4522.
> YARN client will still retry for many times on failover even though RM server throw AccessControlException
> -----------------------------------------------------------------------------------------------------------
>
> Key: YARN-5484
> URL: https://issues.apache.org/jira/browse/YARN-5484
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Bob.zhao
>
> 1. Enable yarn.acl.enable
> 2. Set up some queue for users on yarn, for example queue1 only for user1
> 3. Using user1 to submit app to queue1, it can run successfully.
> 4. Change user2 to submit app to queue1, it will not be permit submit to queue1.
> So, At RM server side, it will throw IOException(ClientRMService.java#submitApplication), which is the parent implementation of the AccessControlException(RMAppManager.java#createAndPopulateNewRMApp), this IOException will be threw to client that cause yarn client frequently failover for many times.
> We'b better avoid this behavior that if client got permission deny from server, it should try once and exit, no need to retry.
> This issue was introduced by YARN-4522.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org