[
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.poc.001.patch
I'm posting a POC patch to get early feedback.
I haven't added a config that checks the version of the timeline service yet,
and I need to sort out various configuration parameters a little more.
But assuming those things will be in place later on, please take a look at
whether the timeline service v.2 code/memory/behavior is cleanly turned off if
the timeline service v.2 is disabled. I would greatly appreciate your feedback.
Thanks!
> 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.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)
