[
https://issues.apache.org/jira/browse/YARN-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951320#comment-15951320
]
Haibo Chen commented on YARN-6377:
----------------------------------
bq. do we have any timeline service related stop on the RM side?
Not sure I understand your question completely. Checking the code, a
timelineCollector in RM is also bound to an application ((RMAppImp) lifecycle.
It is created, started and added to RMTimelineCollectorManager when RMAppImpl
is created, and stopped when RMAppImpl goes to terminal state (FINISHED). When
RMTImelineCollectorManager is stopped, all timelinecollector are stopped and
the underlying timeline writer is closed.
> NMTimelinePublisher#serviceStop does not stop timeline clients
> --------------------------------------------------------------
>
> Key: YARN-6377
> URL: https://issues.apache.org/jira/browse/YARN-6377
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Affects Versions: 3.0.0-alpha2
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Attachments: YARN-6377.01.patch, YARN-6377.02.patch
>
>
> While discussing YARN-6342, Varun found another issue regarding
> TimelineV2Client. "In NMTimelinePublisher#serviceStop though we are not
> explicitly stopping app related timeline clients. I think should be done."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
