[jira] [Commented] (YARN-3045) implement NM writing container lifecycle events and container system metrics to ATS
[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302592#comment-14302592 ] Naganarasimha G R commented on YARN-3045: - Thanks [~sjlee0], for clarification. > implement NM writing container lifecycle events and container system metrics > to ATS > --- > > Key: YARN-3045 > URL: https://issues.apache.org/jira/browse/YARN-3045 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Sangjin Lee >Assignee: Naganarasimha G R > > Per design in YARN-2928, implement NM writing container lifecycle events and > container system metrics to ATS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3045) implement NM writing container lifecycle events and container system metrics to ATS
[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301543#comment-14301543 ] Sangjin Lee commented on YARN-3045: --- In this case, NM would act as a timeline service client, not as a direct aggregator/writer to the backing storage. The idea is for the NM to find the right timeline aggregator, and invoke the timeline service client API to send the timeline events/metrics to that aggregator. That's why the service discovery feature (YARN-3039) is needed for this. Does it help clarify it? > implement NM writing container lifecycle events and container system metrics > to ATS > --- > > Key: YARN-3045 > URL: https://issues.apache.org/jira/browse/YARN-3045 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Sangjin Lee >Assignee: Naganarasimha G R > > Per design in YARN-2928, implement NM writing container lifecycle events and > container system metrics to ATS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3045) implement NM writing container lifecycle events and container system metrics to ATS
[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300808#comment-14300808 ] Naganarasimha G R commented on YARN-3045: - Hi [~sjlee0] Similar to the current plan for RM, planning to have a separate TimelineAggregator for NM and placing it in NM context or in some new class like NMMetricsPublisher. and on different container life cycle events publish ATS entities/events using it. Based on current approach all the app aggregators are in auxillary service and auxillary service cannot capture all life cycle events & metrics, hence i presume we should have per NM TimelineAggregator too. Is there any other approach planned as this is not captured in any jira's or in the doc. > implement NM writing container lifecycle events and container system metrics > to ATS > --- > > Key: YARN-3045 > URL: https://issues.apache.org/jira/browse/YARN-3045 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Sangjin Lee >Assignee: Naganarasimha G R > > Per design in YARN-2928, implement NM writing container lifecycle events and > container system metrics to ATS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
