[YARN-4183] Clarify the behavior of timeline service config properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.1
• Fix Version/s: 2.8.0, 2.7.3, 3.0.0-alpha1
• Target Version/s: 2.7.3
• Hadoop Flags: Reviewed
• Assignee: Naganarasimha G R Assign to me
• Reporter: Mit Desai
• Created: 18/Sep/15 16:27
• Updated: 25/Oct/19 20:26
• Resolved: 31/Mar/16 17:57

Description

Configurations "yarn.timeline-service.enabled" and "yarn.timeline-service.client.best-effort" are not captured better. Currently if the client doesn't want the tokens to be generated for the timeline service they can set "yarn.timeline-service.enabled" to false and/or "yarn.timeline-service.client.best-effort" to true so that even if the ATS is down jobs can continue to get submitted. This functionality is not properly documented, so as part of this jira we try to document and clarify these configurations.

Issue Links

• depends upon: YARN-3623 We should have a config to indicate the Timeline Service version
• relates to: YARN-4356 ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off