[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] [Commented] (YARN-2213) Change proxy-user cookie log in AmIpFilter to DEBUG

[ https://issues.apache.org/jira/browse/YARN-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375785#comment-14375785 ] Xuan Gong commented on YARN-2213: - Could we add {code} if (LOG.isDebugEnabled()) { +

[jira] [Updated] (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:all-tabpanel ] Devaraj K updated YARN-3225: Attachment: YARN-3225-1.patch New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[jira] [Updated] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3136: -- Attachment: 0007-YARN-3136.patch Uploading patch to check findbugs warnings. getTransferredContainers can be a

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375759#comment-14375759 ] Hadoop QA commented on YARN-3136: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2213) Change proxy-user cookie log in AmIpFilter to DEBUG

[ https://issues.apache.org/jira/browse/YARN-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375788#comment-14375788 ] Hadoop QA commented on YARN-2213: - {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (YARN-3389) Two attempts might operate on same data structures concurrently

Jun Gong created YARN-3389: -- Summary: Two attempts might operate on same data structures concurrently Key: YARN-3389 URL: https://issues.apache.org/jira/browse/YARN-3389 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3389) Two attempts might operate on same data structures concurrently

[ https://issues.apache.org/jira/browse/YARN-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3389: --- Attachment: YARN-3389.01.patch Two attempts might operate on same data structures concurrently

[jira] [Updated] (YARN-3384) Test failures since TestLogAggregationService.verifyContainerLogs fails after YARN-2777

[ https://issues.apache.org/jira/browse/YARN-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3384: - Summary: Test failures since TestLogAggregationService.verifyContainerLogs fails after YARN-2777

[jira] [Updated] (YARN-3384) TestLogAggregationService.verifyContainerLogs fails after YARN-2777

[ https://issues.apache.org/jira/browse/YARN-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3384: - Summary: TestLogAggregationService.verifyContainerLogs fails after YARN-2777 (was: Test failures

[jira] [Created] (YARN-3388) userlimit isn't playing well with DRF calculator

Nathan Roberts created YARN-3388: Summary: userlimit isn't playing well with DRF calculator Key: YARN-3388 URL: https://issues.apache.org/jira/browse/YARN-3388 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3384) test case failures in TestLogAggregationService

[ https://issues.apache.org/jira/browse/YARN-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376035#comment-14376035 ] Tsuyoshi Ozawa commented on YARN-3384: -- +1, committing this shortly. test case

[jira] [Commented] (YARN-3384) TestLogAggregationService.verifyContainerLogs fails after YARN-2777

[ https://issues.apache.org/jira/browse/YARN-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376059#comment-14376059 ] Naganarasimha G R commented on YARN-3384: - Thanks [~ozawa], for reviewing and

[jira] [Updated] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3363: Attachment: YARN-3363.000.patch add localization and container launch time to ContainerMetrics at NM to

[jira] [Updated] (YARN-3111) Fix ratio problem on FairScheduler page

[ https://issues.apache.org/jira/browse/YARN-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3111: - Attachment: YARN-3111.v2.patch Fix ratio problem on FairScheduler page

[jira] [Commented] (YARN-3388) userlimit isn't playing well with DRF calculator

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376060#comment-14376060 ] Nathan Roberts commented on YARN-3388: -- Example (lots of things going on in this

[jira] [Commented] (YARN-2777) Mark the end of individual log in aggregated log

[ https://issues.apache.org/jira/browse/YARN-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376066#comment-14376066 ] Hudson commented on YARN-2777: -- SUCCESS: Integrated in Hadoop-trunk-Commit #7402 (See

[jira] [Commented] (YARN-3111) Fix ratio problem on FairScheduler page

[ https://issues.apache.org/jira/browse/YARN-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376086#comment-14376086 ] Hadoop QA commented on YARN-3111: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3384) TestLogAggregationService.verifyContainerLogs fails after YARN-2777

[ https://issues.apache.org/jira/browse/YARN-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376067#comment-14376067 ] Hudson commented on YARN-3384: -- SUCCESS: Integrated in Hadoop-trunk-Commit #7402 (See

[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=14375763#comment-14375763 ] Hadoop QA commented on YARN-3225: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3394) WebApplication proxy documentation is incomplete

[ https://issues.apache.org/jira/browse/YARN-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377320#comment-14377320 ] Tsuyoshi Ozawa commented on YARN-3394: -- +1 for having the document. WebApplication

[jira] [Created] (YARN-3394) WebApplication proxy documentation is incomplete

Bibin A Chundatt created YARN-3394: -- Summary: WebApplication proxy documentation is incomplete Key: YARN-3394 URL: https://issues.apache.org/jira/browse/YARN-3394 Project: Hadoop YARN

[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=14376602#comment-14376602 ] Junping Du commented on YARN-3040: -- Hi [~zjshen], thanks for the patch! I am still

[jira] [Commented] (YARN-3390) RMTimelineCollector should have the context info of each app

[ https://issues.apache.org/jira/browse/YARN-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376684#comment-14376684 ] Zhijie Shen commented on YARN-3390: --- It shouldn't. Storage layer implementations only

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376765#comment-14376765 ] Yongjun Zhang commented on YARN-3021: - Hi [~jianhe], Thanks a lot for the

[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=14376150#comment-14376150 ] Sangjin Lee commented on YARN-3034: --- LGTM. Let's wait to hear from Zhijie. [Collector

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376109#comment-14376109 ] Zhijie Shen commented on YARN-3047: --- bq. We can probably move it to yarn-api. I prefer

[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=14376444#comment-14376444 ] Hadoop QA commented on YARN-3225: - {color:red}-1 overall{color}. Here are the results of

[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=14376169#comment-14376169 ] Zhijie Shen commented on YARN-3040: --- bq. It sounds not quite scalable if we have one

[jira] [Commented] (YARN-3389) Two attempts might operate on same data structures concurrently

[ https://issues.apache.org/jira/browse/YARN-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376180#comment-14376180 ] Hadoop QA commented on YARN-3389: - {color:red}-1 overall{color}. Here are the results of

[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=14376200#comment-14376200 ] Junping Du commented on YARN-3034: -- Thanks [~Naganarasimha] for updating the patch! bq.

[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=14376415#comment-14376415 ] Naganarasimha G R commented on YARN-3034: - Also [~zjshen], earlier thought process

[jira] [Updated] (YARN-3241) FairScheduler handles invalid queue names inconsistently

[ https://issues.apache.org/jira/browse/YARN-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3241: --- Summary: FairScheduler handles invalid queue names inconsistently (was: Leading space,

[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=14376498#comment-14376498 ] Naganarasimha G R commented on YARN-3034: - Thanks for the comments [~zjshen], bq.

[jira] [Commented] (YARN-3024) LocalizerRunner should give DIE action when all resources are localized

[ https://issues.apache.org/jira/browse/YARN-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376556#comment-14376556 ] Karthik Kambatla commented on YARN-3024: [~chengbing.liu] - thanks for the

[jira] [Commented] (YARN-3362) Add node label usage in RM CapacityScheduler web UI

[ https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376563#comment-14376563 ] Naganarasimha G R commented on YARN-3362: - Thanks for the feedback [~leftnoteasy],

[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=14376446#comment-14376446 ] Zhijie Shen commented on YARN-3034: --- bq. so i think its not an incompatible change.

[jira] [Commented] (YARN-3336) FileSystem memory leak in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376447#comment-14376447 ] zhihai xu commented on YARN-3336: - Thanks [~cnauroth] for valuable feedback and committing

[jira] [Commented] (YARN-3241) Leading space, trailing space and empty sub queue name may cause MetricsException for fair scheduler

[ https://issues.apache.org/jira/browse/YARN-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376559#comment-14376559 ] Karthik Kambatla commented on YARN-3241: +1. Checking this in. Leading space,

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375465#comment-14375465 ] zhihai xu commented on YARN-3363: - I uploaded a new patch YARN-3363.000.patch for review.

[jira] [Created] (YARN-3387) container complete message couldn't pass to am if am restarted and rm changed

sandflee created YARN-3387: -- Summary: container complete message couldn't pass to am if am restarted and rm changed Key: YARN-3387 URL: https://issues.apache.org/jira/browse/YARN-3387 Project: Hadoop YARN

[jira] [Commented] (YARN-3363) add localization and container launch time to ContainerMetrics at NM to show these timing information for each active container.

[ https://issues.apache.org/jira/browse/YARN-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375493#comment-14375493 ] Hadoop QA commented on YARN-3363: - {color:red}-1 overall{color}. Here are the results of

[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=14376749#comment-14376749 ] Sangjin Lee commented on YARN-3040: --- Thanks [~zjshen] for the updated patch! I am

[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=14376575#comment-14376575 ] Zhijie Shen commented on YARN-3034: --- bq. then only way RMTimelineCollector can be invoked

[jira] [Commented] (YARN-3241) FairScheduler handles invalid queue names inconsistently

[ https://issues.apache.org/jira/browse/YARN-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376577#comment-14376577 ] Hudson commented on YARN-3241: -- FAILURE: Integrated in Hadoop-trunk-Commit #7406 (See

[jira] [Commented] (YARN-3390) RMTimelineCollector should have the context info of each app

[ https://issues.apache.org/jira/browse/YARN-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376670#comment-14376670 ] Li Lu commented on YARN-3390: - Hi [~zjshen], could you please confirm that this JIRA will also

[jira] [Commented] (YARN-2868) FairScheduler: Metric for latency to allocate first container for an application

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376672#comment-14376672 ] Hudson commented on YARN-2868: -- FAILURE: Integrated in Hadoop-trunk-Commit #7407 (See

[jira] [Created] (YARN-3392) Change NodeManager metrics to not populate resource usage metrics if they are unavailable

Anubhav Dhoot created YARN-3392: --- Summary: Change NodeManager metrics to not populate resource usage metrics if they are unavailable Key: YARN-3392 URL: https://issues.apache.org/jira/browse/YARN-3392

[jira] [Created] (YARN-3393) Getting application(s) goes wrong when app finishes before starting the attempt

Zhijie Shen created YARN-3393: - Summary: Getting application(s) goes wrong when app finishes before starting the attempt Key: YARN-3393 URL: https://issues.apache.org/jira/browse/YARN-3393 Project:

[jira] [Commented] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376605#comment-14376605 ] Wangda Tan commented on YARN-2495: -- Hmm.. {{StringArrayProto.stringElement - elements}} is

[jira] [Commented] (YARN-3383) AdminService should use warn instead of info to log exception when operation fails

[ https://issues.apache.org/jira/browse/YARN-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376629#comment-14376629 ] Hadoop QA commented on YARN-3383: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2868) FairScheduler: Metric for latency to allocate first container for an application

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2868: --- Summary: FairScheduler: Metric for latency to allocate first container for an application

[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=14376695#comment-14376695 ] Anubhav Dhoot commented on YARN-3304: - Hi [~djp] [~vinodkv], If we use a default of

[jira] [Updated] (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:all-tabpanel ] Sangjin Lee updated YARN-3391: -- Description: To continue the discussion in YARN-3040, let's figure out the best way to describe the

[jira] [Updated] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated YARN-3021: Attachment: YARN-3021.006.patch YARN's delegation-token handling disallows certain trust setups to

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376633#comment-14376633 ] Karthik Kambatla commented on YARN-2868: +1, checking this in. Add metric for

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376719#comment-14376719 ] Li Lu commented on YARN-3047: - Hi [~varun_saxena], thanks for the new patch. Could you please

[jira] [Commented] (YARN-3241) FairScheduler handles invalid queue names inconsistently

[ https://issues.apache.org/jira/browse/YARN-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376737#comment-14376737 ] zhihai xu commented on YARN-3241: - Thanks [~kasha] for valuable feedback and committing the

[jira] [Updated] (YARN-3387) container complete message couldn't pass to am if am restarted and rm changed

[ https://issues.apache.org/jira/browse/YARN-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3387: --- Priority: Critical (was: Major) Target Version/s: 2.7.0 container complete

[jira] [Commented] (YARN-3387) container complete message couldn't pass to am if am restarted and rm changed

[ https://issues.apache.org/jira/browse/YARN-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376640#comment-14376640 ] Karthik Kambatla commented on YARN-3387: Does this imply our work-preserving AM

[jira] [Updated] (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:all-tabpanel ] Zhijie Shen updated YARN-3040: -- Attachment: YARN-3040.3.patch Upload a new patch to address the comments so far. The notable change in

[jira] [Commented] (YARN-3386) Cgroups feature should work with default hierarchy settings of CentOS 7

[ https://issues.apache.org/jira/browse/YARN-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376645#comment-14376645 ] Karthik Kambatla commented on YARN-3386: YARN-2194 seems to imply there are more

[jira] [Updated] (YARN-3383) AdminService should use warn instead of info to log exception when operation fails

[ https://issues.apache.org/jira/browse/YARN-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3383: Attachment: YARN-3383-032315.patch Rebase the patch with the latest trunk. AdminService should use warn instead

[jira] [Assigned] (YARN-2605) [RM HA] Rest api endpoints doing redirect incorrectly

[ https://issues.apache.org/jira/browse/YARN-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2605: --- Assignee: Anubhav Dhoot [RM HA] Rest api endpoints doing redirect incorrectly

[jira] [Updated] (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:all-tabpanel ] Sangjin Lee updated YARN-3391: -- Description: To continue the discussion in YARN-3040, let's figure out the best way to describe the

[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=14376229#comment-14376229 ] Naganarasimha G R commented on YARN-3034: - Thanks [~sjlee0] [~djp] for the

[jira] [Updated] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3136: -- Attachment: 0008-YARN-3136.patch getTransferredContainers can be a bottleneck during AM registration

[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=14376228#comment-14376228 ] Zhijie Shen commented on YARN-3034: --- Let me elaborate my previous comments. In YARN-3040,

[jira] [Commented] (YARN-3390) RMTimelineCollector should have the context info of each app

[ https://issues.apache.org/jira/browse/YARN-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376323#comment-14376323 ] Naganarasimha G R commented on YARN-3390: - Hi [~zjshen], Shall i work on this jira

[jira] [Created] (YARN-3390) RMTimelineCollector should have the context info of each app

Zhijie Shen created YARN-3390: - Summary: RMTimelineCollector should have the context info of each app Key: YARN-3390 URL: https://issues.apache.org/jira/browse/YARN-3390 Project: Hadoop YARN

[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=14376280#comment-14376280 ] Sangjin Lee commented on YARN-3040: --- {quote} I can understand this particular case

[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=14376400#comment-14376400 ] Zhijie Shen commented on YARN-3040: --- [~sjlee0], thanks for more comments, but would you

[jira] [Commented] (YARN-3336) FileSystem memory leak in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376300#comment-14376300 ] Hudson commented on YARN-3336: -- FAILURE: Integrated in Hadoop-trunk-Commit #7405 (See

[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=14376349#comment-14376349 ] Naganarasimha G R commented on YARN-3034: - Thanks for your comments [~zjshen] bq.

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

Zhijie Shen created YARN-3391: - Summary: Clearly define flow ID/ flow run / flow version in API and storage Key: YARN-3391 URL: https://issues.apache.org/jira/browse/YARN-3391 Project: Hadoop YARN

[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.patch Deliver a quick patch to fix it, given this is a blocker for release.

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376380#comment-14376380 ] Hadoop QA commented on YARN-3136: - {color:red}-1 overall{color}. Here are the results of

[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=14376256#comment-14376256 ] Zhijie Shen commented on YARN-3034: --- Some comments about the patch: 1.

[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=14376255#comment-14376255 ] Sangjin Lee commented on YARN-3040: --- bq. I can see the benefit. For example, if it

[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=14376285#comment-14376285 ] Sangjin Lee commented on YARN-3040: --- {quote} I can understand this particular case

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376402#comment-14376402 ] Naganarasimha G R commented on YARN-3044: - Hi [~zjshen] [~sjlee0], As part of this

[jira] [Commented] (YARN-3383) AdminService should use warn instead of info to log exception when operation fails

[ https://issues.apache.org/jira/browse/YARN-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376830#comment-14376830 ] Hadoop QA commented on YARN-3383: - {color:red}-1 overall{color}. Here are the results of

[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=14376920#comment-14376920 ] Junping Du commented on YARN-3304: -- Thanks [~adhoot] for comments! bq. If we use a default

[jira] [Commented] (YARN-2901) Add errors and warning stats to RM, NM web UI

[ https://issues.apache.org/jira/browse/YARN-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377040#comment-14377040 ] Wangda Tan commented on YARN-2901: -- Hi [~vvasudev], I spent some time take a look at

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376944#comment-14376944 ] Hadoop QA commented on YARN-3021: - {color:red}-1 overall{color}. Here are the results of

[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=14376973#comment-14376973 ] Karthik Kambatla commented on YARN-3304: bq. That's an incompatible change which

[jira] [Updated] (YARN-3347) Improve YARN log command to get AMContainer logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3347: Attachment: YARN-3347.2.patch fix -1 on findBug Improve YARN log command to get AMContainer logs

[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=14377008#comment-14377008 ] Hadoop QA commented on YARN-3304: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3387) container complete message couldn't pass to am if am restarted and rm changed

[ https://issues.apache.org/jira/browse/YARN-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377019#comment-14377019 ] sandflee commented on YARN-3387: yes container complete message couldn't pass to am if am

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377031#comment-14377031 ] Hadoop QA commented on YARN-3347: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3336) FileSystem memory leak in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14376914#comment-14376914 ] Chris Nauroth commented on YARN-3336: - [~zxu], I apologize, but I missed entering your

[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-v2.patch Update patch to v2 to fix the test failure for 1st patch.

[jira] [Updated] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated YARN-3021: Attachment: YARN-3021.006.patch The test failure seems to be unrelated, upload same patch 06 to

[jira] [Updated] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly over DistCp

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated YARN-3021: Attachment: (was: YARN-3021.006.patch) YARN's delegation-token handling disallows certain trust

[jira] [Updated] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3244: Attachment: YARN-3244.2.patch Address all the latest comments Add user specified information for clean-up

[jira] [Commented] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377175#comment-14377175 ] Hadoop QA commented on YARN-3244: - {color:green}+1 overall{color}. Here are the results of

[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=14377196#comment-14377196 ] Naganarasimha G R commented on YARN-3034: - Hi [~zjshen], bq. According to this

[jira] [Commented] (YARN-3393) Getting application(s) goes wrong when app finishes before starting the attempt

[ https://issues.apache.org/jira/browse/YARN-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377216#comment-14377216 ] Hudson commented on YARN-3393: -- FAILURE: Integrated in Hadoop-trunk-Commit #7409 (See

[jira] [Updated] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-2495: Attachment: YARN-2495.20150324-1.patch Allow admin specify labels from each NM (Distributed

[jira] [Commented] (YARN-3244) Add user specified information for clean-up container in ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14377098#comment-14377098 ] Xuan Gong commented on YARN-3244: - Created a new object named CleanupContainer which

  1   2   >