[YARN-5484] YARN client will still retry for many times on failover even though RM server throw AccessControlException

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.9.0
• Target Version/s: 2.9.0
• Assignee: Unassigned
• Reporter: Bob.zhao
• Created: 08/Aug/16 13:11
• Updated: 08/Aug/16 16:54
• Resolved: 08/Aug/16 16:54

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.

Issue Links

• duplicates: YARN-4833 For Queue AccessControlException client retries multiple times on both RM
• is broken by: YARN-4522 Queue acl can be checked at app submission
• is duplicated by: YARN-4833 For Queue AccessControlException client retries multiple times on both RM