[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350624#comment-14350624 ] Junping Du commented on YARN-3276: -- Another reason that we cannot merge two TimelineUtils

[jira] [Created] (YARN-3304) Default return values for resources in ResourceCalculatorProcessTree are inconsistent in case where functionality is not available.

Junping Du created YARN-3304: Summary: Default return values for resources in ResourceCalculatorProcessTree are inconsistent in case where functionality is not available. Key: YARN-3304 URL:

[jira] [Commented] (YARN-3296) yarn.nodemanager.container-monitor.process-tree.class is configurable but ResourceCalculatorProcessTree class is marked Private

[ https://issues.apache.org/jira/browse/YARN-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14352289#comment-14352289 ] Junping Du commented on YARN-3296: -- bq. I am open to doing it in another JIRA. It won't be

[jira] [Commented] (YARN-3296) yarn.nodemanager.container-monitor.process-tree.class is configurable but ResourceCalculatorProcessTree class is marked Private

[ https://issues.apache.org/jira/browse/YARN-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351856#comment-14351856 ] Junping Du commented on YARN-3296: -- Thanks [~hitesh] for updating the patch! bq. There is

[jira] [Commented] (YARN-3034) [Aggregator wireup] Implement RM starting its ATS writer

[ https://issues.apache.org/jira/browse/YARN-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360822#comment-14360822 ] Junping Du commented on YARN-3034: -- Hi [~vinodkv], for DistributedShell patch, we have

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14360686#comment-14360686 ] Junping Du commented on YARN-3225: -- bq. If we have a constraint that we should issue

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361089#comment-14361089 ] Junping Du commented on YARN-3225: -- One additional comments: For RMNodeEventType,

[jira] [Updated] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3212: - Attachment: YARN-3212-v1.patch Upload the first patch for core state changes with decommissioning. For

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14361353#comment-14361353 ] Junping Du commented on YARN-3039: -- bq. Yes, I get the reasoning for annotating individual

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14356179#comment-14356179 ] Junping Du commented on YARN-3039: -- Hi [~sjlee0], thanks for comments above. I think we

[jira] [Commented] (YARN-2928) Application Timeline Server (ATS) next gen: phase 1

[ https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14356193#comment-14356193 ] Junping Du commented on YARN-2928: -- bq. let me know if you are OK with the name, and I can

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14356255#comment-14356255 ] Junping Du commented on YARN-3225: -- Thanks [~devaraj.k]. Sorry for missing an important

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: YARN-3039-v4.patch Upload v4 patch with necessary unit tests, especially end-to-end test. This

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14356774#comment-14356774 ] Junping Du commented on YARN-3225: -- bq. Here what would happen to the decommissioning node

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359957#comment-14359957 ] Junping Du commented on YARN-3039: -- Also, thanks [~zjshen] for the comments! bq. Sorry for

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359936#comment-14359936 ] Junping Du commented on YARN-3039: -- [~sjlee0], Thanks for comments here! In my

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359239#comment-14359239 ] Junping Du commented on YARN-3225: -- Nice discussion, [~devaraj.k]! bq. If there are some

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14359163#comment-14359163 ] Junping Du commented on YARN-3039: -- Thanks [~sjlee0] for review and many good comments! I

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: YARN-3039-v5.patch Update v5 patch with incorporating [~sjlee0]'s comments. [Aggregator

[jira] [Commented] (YARN-3034) [Collector wireup] Implement RM starting its timeline collector

[ https://issues.apache.org/jira/browse/YARN-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377920#comment-14377920 ] Junping Du commented on YARN-3034: -- Thanks [~Naganarasimha] for updating the patch! Latest

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377753#comment-14377753 ] Junping Du commented on YARN-3304: -- Thanks for comments, [~kasha]! bq. In previous

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377984#comment-14377984 ] Junping Du commented on YARN-3040: -- Some additional comments: {code} property +

[jira] [Updated] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3212: - Attachment: YARN-3212-v3.patch Update patch to address review comments above, include: - Properly handling

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14379860#comment-14379860 ] Junping Du commented on YARN-3225: -- Thanks [~devaraj.k] for updating the patch! Sorry for

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380102#comment-14380102 ] Junping Du commented on YARN-3225: -- Thanks for quickly response, [~devaraj.k]! bq. If we

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380129#comment-14380129 ] Junping Du commented on YARN-3212: -- The test failure is not related to the patch here and

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380194#comment-14380194 ] Junping Du commented on YARN-3040: -- Thanks [~zjshen] for updating the patch! bq. I also

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380635#comment-14380635 ] Junping Du commented on YARN-3040: -- bq. How about we check if cluster-id is set, and if

[jira] [Commented] (YARN-3399) Default cluster ID for RM HA

[ https://issues.apache.org/jira/browse/YARN-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380788#comment-14380788 ] Junping Du commented on YARN-3399: -- I would also suggest to deprecate existing

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380816#comment-14380816 ] Junping Du commented on YARN-3040: -- To be clear, the behavior for without setting

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14380880#comment-14380880 ] Junping Du commented on YARN-3040: -- bq. I am +1 for having a stable default value if users

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v8.patch There are still two issues with v7 version: 1. cpuTimeMs in

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386847#comment-14386847 ] Junping Du commented on YARN-3304: -- Hi [~adhoot], [~kasha] and [~vinodkv], I am sure v8

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387509#comment-14387509 ] Junping Du commented on YARN-3304: -- Let's do here. I will upload a quick patch soon.

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-appendix.patch Upload an appendix patch to address [~hitesh] and [~vinodkv]'s

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387832#comment-14387832 ] Junping Du commented on YARN-3334: -- Sorry for coming late as having a pending fix on 2.7

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-appendix-v2.patch appendix-v2 suppress the warning of calling deprecated methods.

[jira] [Updated] (YARN-3334) [Event Producers] NM start to posting some app related metrics in early POC stage of phase 2.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3334: - Attachment: YARN-3334-v2.patch [Event Producers] NM start to posting some app related metrics in early

[jira] [Commented] (YARN-3040) [Data Model] Make putEntities operation be aware of the app's context

[ https://issues.apache.org/jira/browse/YARN-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14382191#comment-14382191 ] Junping Du commented on YARN-3040: -- OK. I have commit v6 patch to branch YARN-2928. Thanks

[jira] [Updated] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3334: - Description: After YARN-3039, we have service discovery mechanism to pass app-collector service address

[jira] [Commented] (YARN-3334) [Event Producers] NM start to posting some app related metrics in early POC stage of phase 2.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14382171#comment-14382171 ] Junping Du commented on YARN-3334: -- Thanks [~zjshen] for review and comments! In v2, I

[jira] [Assigned] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3304: Assignee: Junping Du (was: Karthik Kambatla) ResourceCalculatorProcessTree#getCpuUsagePercent

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383762#comment-14383762 ] Junping Du commented on YARN-3304: -- Thanks [~adhoot] for comments. bq. Overall the API

[jira] [Updated] (YARN-3407) HttpServer2 Max threads in TimelineCollectorManager should be more than 10

[ https://issues.apache.org/jira/browse/YARN-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3407: - Affects Version/s: YARN-2928 HttpServer2 Max threads in TimelineCollectorManager should be more than 10

[jira] [Created] (YARN-3408) TestDistributedShell get failed due to RM start failure.

Junping Du created YARN-3408: Summary: TestDistributedShell get failed due to RM start failure. Key: YARN-3408 URL: https://issues.apache.org/jira/browse/YARN-3408 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3334: - Attachment: YARN-3334-v4.patch Update the patch to address major comments above, except ContainerEntity

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389361#comment-14389361 ] Junping Du commented on YARN-3304: -- bq. We do not need to explicitly say so for each

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14388509#comment-14388509 ] Junping Du commented on YARN-3304: -- I would like to get appendix (v2) patch in not only

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-appendix-v3.patch ResourceCalculatorProcessTree#getCpuUsagePercent default return

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-appendix-v4.patch Murphy's law appears again... :( Javac warning is valid but

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389540#comment-14389540 ] Junping Du commented on YARN-3334: -- Reply to [~sjlee0]'s previous comments: bq.

[jira] [Commented] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389545#comment-14389545 ] Junping Du commented on YARN-3334: -- Please hold on reviewing v4 patch, it need some

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385263#comment-14385263 ] Junping Du commented on YARN-3304: -- There is an small issue for getCumulativeCpuTime() in

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385275#comment-14385275 ] Junping Du commented on YARN-3304: -- Wait... Sounds like getCumulativeCpuTime() is proper

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v6-with-rename.patch Upload another v6 patch with renaming work. Filed

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v6-no-rename.patch Upload v6 patch include fix above issue and integrating with MR

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v7.patch Thanks [~adhoot] for review and comments! Fix your two comments above in v7

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385382#comment-14385382 ] Junping Du commented on YARN-3304: -- v7 should apply the latest trunk. Manually kick off

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375867#comment-14375867 ] Junping Du commented on YARN-3304: -- Hi [~vinodkv], agree that we can fix it as 0 to keep

[jira] [Updated] (YARN-3334) [Event Producers] NM TimelineClient life cycle handling and container metrics posting to new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3334: - Attachment: YARN-3334-v5.patch Upload v5 patch with addressing all review comments above. For using

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390844#comment-14390844 ] Junping Du commented on YARN-3391: -- Thanks [~zjshen] for delivering the patch! To be

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390936#comment-14390936 ] Junping Du commented on YARN-3391: -- Thanks [~sjlee0] for reply quickly! That helps a lot.

[jira] [Updated] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Summary: Refactor and fix null casting in some map cast for TimelineEntity (old and new) (was: Fix NPE

[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344075#comment-14344075 ] Junping Du commented on YARN-3276: -- Fix title to reflect what we discussion above. Thanks

[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344167#comment-14344167 ] Junping Du commented on YARN-3276: -- Just found the PackageInfo in existing TimelineUtils

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345345#comment-14345345 ] Junping Du commented on YARN-3031: -- Hi [~vrushalic], Awesome! I will help to review this

[jira] [Commented] (YARN-3116) [Aggregator wireup] We need an assured way to determine if a container is an AM container on NM

[ https://issues.apache.org/jira/browse/YARN-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343272#comment-14343272 ] Junping Du commented on YARN-3116: -- I think we can consider to add an optional field in

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340408#comment-14340408 ] Junping Du commented on YARN-3125: -- Thanks [~gtCarrera9] for adding a UT and [~zjshen] for

[jira] [Commented] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340392#comment-14340392 ] Junping Du commented on YARN-3087: -- bq. Similar code also appear in v1 timeline object

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Attachment: YARN-3276.patch Upload a patch to fix it. Fix NPE and refactor in some map cast for

[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

[ https://issues.apache.org/jira/browse/YARN-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3274: - Description: Per discussion in MAPREDUCE-5583, FifoScheduler should assign containers that up to the

[jira] [Updated] (YARN-3274) FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY

[ https://issues.apache.org/jira/browse/YARN-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3274: - Summary: FIFOScheduler should assign the same container number up to ResourceRequest ask for ANY (was:

[jira] [Created] (YARN-3274) FIFOScheduler should assign the same container number equal to ResourceRequest ask for ANY

Junping Du created YARN-3274: Summary: FIFOScheduler should assign the same container number equal to ResourceRequest ask for ANY Key: YARN-3274 URL: https://issues.apache.org/jira/browse/YARN-3274

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Attachment: YARN-3276-v2.patch Thanks [~ozawa] for review and comments! Just add test cases in v2 patch.

[jira] [Updated] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3276: - Target Version/s: YARN-2928 Fix NPE and refactor in some map cast for TimelineEntity

[jira] [Assigned] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3039: Assignee: Junping Du (was: Naganarasimha G R) [Aggregator wireup] Implement ATS app-appgregator

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: YARN-3039-v2-incomplete.patch Update a patch (haven't finished yet) to reflect some of

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347384#comment-14347384 ] Junping Du commented on YARN-3039: -- Thanks [~Naganarasimha] for comments! bq. Even if we

[jira] [Commented] (YARN-3276) Fix NPE and refactor in some map cast for TimelineEntity

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341023#comment-14341023 ] Junping Du commented on YARN-3276: -- Hi [~gtCarrera], you are right that specific case here

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344914#comment-14344914 ] Junping Du commented on YARN-3039: -- Thanks for comments, [~Naganarasimha]! bq. +1 for this

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345160#comment-14345160 ] Junping Du commented on YARN-3031: -- Discussed offline with [~vrushalic] and [~zjshen] last

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1409#comment-1409 ] Junping Du commented on YARN-3039: -- Thanks [~sjlee0] for comments! bq. I'm also thinking

[jira] [Assigned] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3115: Assignee: Junping Du (was: Zhijie Shen) [Aggregator wireup] Work-preserving restarting of

[jira] [Commented] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333529#comment-14333529 ] Junping Du commented on YARN-3115: -- Thanks [~zjshen]! Taking it over. Looks like it

[jira] [Updated] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3115: - Assignee: Zhijie Shen (was: Junping Du) [Aggregator wireup] Work-preserving restarting of per-node

[jira] [Assigned] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3115: Assignee: Junping Du (was: Zhijie Shen) [Aggregator wireup] Work-preserving restarting of

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: YARN-3039-no-test.patch Just finish the first patch with core changes needed in option 2

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335400#comment-14335400 ] Junping Du commented on YARN-3125: -- Talked offline to Zhijie to take over this JIRA.

[jira] [Updated] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3125: - Attachment: YARN-3125.patch Based on latest timelineservice put API provided in YARN-3240 [Event

[jira] [Assigned] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-3125: Assignee: Junping Du (was: Zhijie Shen) [Event producers] Change distributed shell to use new

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336707#comment-14336707 ] Junping Du commented on YARN-3039: -- Thanks [~Naganarasimha] and [~rkanter] for review and

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Summary: [Aggregator wireup] Implement ATS app-appgregator service discovery (was: [Aggregator wireup]

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336994#comment-14336994 ] Junping Du commented on YARN-3031: -- Hi [~vrushalic], thanks for updating the patch. A

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329084#comment-14329084 ] Junping Du commented on YARN-3039: -- Hi [~rkanter], thanks for sharing your thoughts here.

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Attachment: Service Binding for applicationaggregator of ATS (draft).pdf I put some thoughts into a draft

[jira] [Commented] (YARN-3115) [Aggregator wireup] Work-preserving restarting of per-node aggregator

[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329103#comment-14329103 ] Junping Du commented on YARN-3115: -- Hi [~zjshen], do you already start the work on this?

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335010#comment-14335010 ] Junping Du commented on YARN-3039: -- Thanks [~zjshen] for review and comments! bq. I think

[jira] [Commented] (YARN-3240) [Data Mode] Implement client API to put generic entities

[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335106#comment-14335106 ] Junping Du commented on YARN-3240: -- Thanks [~zjshen] for the patch! I am reviewing this

[jira] [Commented] (YARN-3087) [Aggregator implementation] the REST server (web server) for per-node aggregator does not work if it runs inside node manager

[ https://issues.apache.org/jira/browse/YARN-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338686#comment-14338686 ] Junping Du commented on YARN-3087: -- Thanks [~gtCarrera9] for updating the patch! Just

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338654#comment-14338654 ] Junping Du commented on YARN-3031: -- bq. The AggregateUpTo enum has the tracks to aggregate

<    4   5   6   7   8   9   10   11   12   13   >