[YARN-4356] ensure the timeline service v.2 is disabled cleanly and has no impact when it's turned off

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: YARN-2928
• Fix Version/s: 2.9.0, 3.0.0-alpha1
• Component/s: timelineserver
• Labels: yarn-2928-1st-milestone
• Hadoop Flags: Reviewed
• Assignee: Sangjin Lee
• Reporter: Sangjin Lee
• Created: 13/Nov/15 20:00
• Updated: 25/Oct/19 20:25
• Resolved: 11/Dec/15 19:22

Description

For us to be able to merge the first milestone drop to trunk, we want to ensure that once disabled the timeline service v.2 has no impact from the server side to the client side. If the timeline service is not enabled, no action should be done. If v.1 is enabled but not v.2, v.1 should behave the same as it does before the merge.

Issue Links

• is related to: YARN-5726 Test exception in TestContainersMonitorResourceChange.testContainersResourceChange when trying to get NMTimelinePublisher
• is related to: YARN-4183 Clarify the behavior of timeline service config properties
• is related to: YARN-3623 We should have a config to indicate the Timeline Service version
• relates to: YARN-4368 Support Multiple versions of the timeline service at the same time