[YARN-5162] Fix Exceptions thrown during registerAM call when Distributed Scheduling is Enabled

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha1
• Assignee: Hitesh Sharma
• Reporter: Arun Suresh
• Created: 26/May/16 14:07
• Updated: 13/Nov/17 23:08
• Resolved: 02/Jun/16 16:17

Description

The following Exception is seen and the AM fails to register with RM:

16/05/24 17:09:26 INFO ipc.Server: Auth successful for appattempt_1464108777756_0001_000001 (auth:SIMPLE)
16/05/24 17:09:26 INFO amrmproxy.AMRMProxyService: Registering application master. Host: Port:0 Tracking Url:
16/05/24 17:09:26 INFO amrmproxy.DefaultRequestInterceptor: Forwarding registration request to the real YARN RM
16/05/24 17:09:26 DEBUG nodemanager.NodeStatusUpdaterImpl: Node's health-status : true,
16/05/24 17:09:26 DEBUG nodemanager.NodeStatusUpdaterImpl: Sending out 1 container statuses: [ContainerStatus: [ContainerId: container_1464108777756_0001_01_000
001, ExecutionType: GUARANTEED, State: RUNNING, Capability: <memory:1024, vCores:1>, Diagnostics: , ExitStatus: -1000, ]]
16/05/24 17:09:26 WARN ipc.Client: Exception encountered while connecting to the server : org.apache.hadoop.security.AccessControlException: Client cannot authe
nticate via:[TOKEN]