YARN-6736, RM support writing into ats v1 and v2 by new configuration setting yarn.timeline-service.versions.
Couple of issues observed in deployment are
- TimelineClientImpl doesn't honor newly added configuration rather it still get version number from yarn.timeline-service.version. This causes not writing into v1.5 API's even though yarn.timeline-service.versions has 1.5 value.
- Similar line from 1st point, TimelineUtils#timelineServiceV1_5Enabled doesn't honor timeline-service.versions.
- JobHistoryEventHandler#serviceInit(), line no 271 check for version number rather than calling YarnConfiguration#timelineServiceV2Enabled
cc :/ Aaron Gresch