[YARN-1256] NM silently ignores non-existent service in StartContainerRequest

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.1-beta
• Fix Version/s: 2.2.0
• Hadoop Flags: Reviewed
• Assignee: Xuan Gong
• Reporter: Bikas Saha
• Created: 30/Sep/13 22:27
• Updated: 30/Jun/15 07:20
• Resolved: 04/Oct/13 00:24

Description

A container can set token service metadata for a service, say shuffle_service. If that service does not exist then the errors is silently ignored. Later, when the next container wants to access data written to shuffle_service by the first task, then it fails because the service does not have the token that was supposed to be set by the first task.