[YARN-3623] We should have a config to indicate the Timeline Service version

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: timelineserver
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed

Release Note

Add a new configuration "yarn.timeline-service.version" to indicate what is the current version of the running timeline service. For example, if "yarn.timeline-service.version" is 1.5, and "yarn.timeline-service.enabled" is true, it means the cluster will and should bring up the timeline service v.1.5. On the client side, if the client uses the same version of timeline service, it should succeed. If the client chooses to use a smaller version in spite of this, then depending on how robust the compatibility story is between versions, the results may vary.

• Assignee: Xuan Gong
• Reporter: Zhijie Shen
• Created: 11/May/15 21:55
• Updated: 25/Oct/19 20:25
• Resolved: 10/Dec/15 11:00

Description

So far RM, MR AM, DA AM added/changed new config to enable the feature to write the timeline data to v2 server. It's good to have a YARN timeline-service.version config like timeline-service.enable to indicate the version of the running timeline service with the given YARN cluster. It's beneficial for users to more smoothly move from v1 to v2, as they don't need to change the existing config, but switch this config from v1 to v2. And each framework doesn't need to have their own v1/v2 config.

Issue Links

• is depended upon by: YARN-4368 Support Multiple versions of the timeline service at the same time
• is depended upon by: YARN-4234 New put APIs in TimelineClient for ats v1.5
• is depended upon by: YARN-4183 Clarify the behavior of timeline service config properties
• relates to: YARN-4356 ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off