hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7476) Fix miscellaneous issues in ATSv2 after merge to branch-2
Date Sun, 12 Nov 2017 08:50:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248814#comment-16248814
] 

Varun Saxena commented on YARN-7476:
------------------------------------

Test failures are unrelated to the patch.
However, the test failure can be simulated and happens only on branch-2. It passes on trunk.

> Fix miscellaneous issues in ATSv2 after merge to branch-2
> ---------------------------------------------------------
>
>                 Key: YARN-7476
>                 URL: https://issues.apache.org/jira/browse/YARN-7476
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-7476-branch-2.01.patch
>
>
>     a) We are still using Resource#getMemory in NMTimelinePublisher#publishContainerCreatedEvent.
This has been deprecated since YARN-4844. Better to use getMemorySize instead.
>     b) Post YARN-5865, application priority should be fetched from RMAppImpl instead
of app submission context. But we are still fetching it from submission context while publishing
entities to timeline service. This would mean that if priority is updated, it will not be
published to timeline service.
>     c) The order of app_collectors in NodeHeartbeatResponseProto is different from trunk.
Better to make it consistent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message