[ 
https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sangjin Lee updated YARN-4356:
------------------------------
    Attachment: YARN-4356-feature-YARN-2928.002.patch

Posted patch v.2. This should be a reasonably complete patch.

Changes since v.1:
- added TIMELINE_SERVICE_VERSION config per YARN-3623
- removed MAPREDUCE_JOB_NEW_TIMELINE_SERVICE_ENABLED and had MR use the 
timeline service version
- removed the command line flag in distributed shell, and had it rely on the 
timeline service version instead
- clarified the purpose of SYSTEM_METRICS_PUBLISHER_ENABLED to be about 
controlling the subfeature of publishing the system events/metrics under 
timeline service v.2
- clarified the purpose of RM_SYSTEM_METRICS_PUBLISHER_ENABLED to be about 
controlling the subfeature of publishing the system events/metrics by RM under 
timeline service v.1
- added checks for the timeline v.2 config in the timeline collector service 
and the reader server
- fixed a NPE in NodeStatusUpdaterImpl.updateTimelineClientsAddress()


> ensure the timeline service v.2 is disabled cleanly and has no impact when 
> it's turned off
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-4356
>                 URL: https://issues.apache.org/jira/browse/YARN-4356
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Critical
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-4356-feature-YARN-2928.002.patch, 
> YARN-4356-feature-YARN-2928.poc.001.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to