[HADOOP-12697] IPC retry policies should recognise that SASL auth failures are unrecoverable

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.7.1
• Component/s: ipc

Environment

Cluster with kerberos on and client not calling with the right credentials

• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 08/Jan/16 11:14
• Updated: 05/Feb/16 15:35
• Resolved: 05/Feb/16 15:35

Description

SLIDER-1050 shows that if you don't have the right kerberos settings, the Yarn client IPC channel blocks retrying to the talk to the RM, retrying repeatedly

2016-01-07 02:50:45,111 [main] WARN  ipc.Client - Exception encountered while connecting to the server :
 javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException:
 No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]

SASL exceptions need to be recognised as irreconcilable authentication failures, rather than generic IOEs that might go away if you retry

Issue Links

• duplicates: HADOOP-10036 RetryInvocationHandler should recognise that there is no point retrying to auth failures
• is related to: YARN-4558 Yarn client retries on some non-retriable exceptions
• is related to: HADOOP-12054 RPC client should not retry for InvalidToken exceptions
• relates to: SLIDER-1026 AM can't make YarnClient calls on a secure cluster