[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025583#comment-15025583 ] Inigo Goiri commented on YARN-3980: --- Thank you for taking care of this! > Plumb resource-utilization

[jira] [Updated] (YARN-4132) Nodemanagers should try harder to connect to the RM

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4132: - Component/s: nodemanager Issue Type: Improvement (was: Bug) +1 latest patch lgtm. Committing this.

[jira] [Updated] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4132: - Hadoop Flags: Reviewed Summary: Separate configs for nodemanager to resourcemanager connection

[jira] [Commented] (YARN-4343) Need to support Application History Server on ATSV2

[ https://issues.apache.org/jira/browse/YARN-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025619#comment-15025619 ] Sangjin Lee commented on YARN-4343: --- And if so, you might want to reword the title of this JIRA to

[jira] [Commented] (YARN-4343) Need to support Application History Server on ATSV2

[ https://issues.apache.org/jira/browse/YARN-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025614#comment-15025614 ] Sangjin Lee commented on YARN-4343: --- So if I understood correctly, what we're discussing here is to

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025638#comment-15025638 ] Hadoop QA commented on YARN-4304: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

Xuan Gong created YARN-4392: --- Summary: ApplicationCreatedEvent event time resets after RM restart/failover Key: YARN-4392 URL: https://issues.apache.org/jira/browse/YARN-4392 Project: Hadoop YARN

[jira] [Updated] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4392: Attachment: YARN-4392-2015-11-24.patch > ApplicationCreatedEvent event time resets after RM restart/failover

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

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

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025669#comment-15025669 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #718 (See

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025714#comment-15025714 ] Hadoop QA commented on YARN-4365: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Comment Edited] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025761#comment-15025761 ] Xuan Gong edited comment on YARN-4392 at 11/25/15 12:05 AM: We would see those

[jira] [Commented] (YARN-4375) CapacityScheduler needs more debug logging for why queues don't get containers

[ https://issues.apache.org/jira/browse/YARN-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025743#comment-15025743 ] Hadoop QA commented on YARN-4375: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025761#comment-15025761 ] Xuan Gong commented on YARN-4392: - We would see those only when the following two conditions happens are

[jira] [Commented] (YARN-4390) Consider container request size during CS preemption

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025542#comment-15025542 ] Bikas Saha commented on YARN-4390: -- I am not sure if this is a bug as described. If preemption does free

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025722#comment-15025722 ] Jason Lowe commented on YARN-4365: -- +1 latest patch lgtm. Committing this. > FileSystemNodeLabelStore

[jira] [Commented] (YARN-4248) REST API for submit/update/delete Reservations

[ https://issues.apache.org/jira/browse/YARN-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025746#comment-15025746 ] Chris Douglas commented on YARN-4248: - * Would it make sense to return 201

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025789#comment-15025789 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1450 (See

[jira] [Updated] (YARN-4375) CapacityScheduler needs more debug logging for why queues don't get containers

[ https://issues.apache.org/jira/browse/YARN-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4375: --- Attachment: YARN-4375.patch [~sunilg], thanks for pointing me to those ongoing efforts. What I want to

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025325#comment-15025325 ] Kuhu Shukla commented on YARN-4365: --- [~jlowe], Request for comments/review. Thanks a lot. >

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025470#comment-15025470 ] Jason Lowe commented on YARN-4365: -- Rather than poking the store into the manager object, we don't need

[jira] [Updated] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4365: -- Attachment: YARN-4365-3.patch Thank you [~jlowe]. Updated the patch. > FileSystemNodeLabelStore should

[jira] [Updated] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4365: -- Attachment: YARN-4365-2.patch Attaching revised patch, with a better test case and changing the scope of

[jira] [Updated] (YARN-4334) Ability to avoid ResourceManager recovery if state store is "too old"

[ https://issues.apache.org/jira/browse/YARN-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4334: --- Attachment: YARN-4334.4.2.patch > Ability to avoid ResourceManager recovery if state store is "too old" >

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025311#comment-15025311 ] Hadoop QA commented on YARN-4365: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: REST_and_UI.zip Attaching REST o/p and UI screen shots. > AM max resource configuration per

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: 0002-YARN-4304.patch Attaching updated version of patch addressing the comments. -

[jira] [Commented] (YARN-4387) Fix typo in FairScheduler log message

[ https://issues.apache.org/jira/browse/YARN-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025403#comment-15025403 ] Hudson commented on YARN-4387: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2575 (See

[jira] [Commented] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025219#comment-15025219 ] Sangjin Lee commented on YARN-3862: --- I agree that currently the config or metric ids are used directly as

[jira] [Created] (YARN-4391) Exception is logged while accessing scheduler RM web UI when Node Labels are configured

Sunil G created YARN-4391: - Summary: Exception is logged while accessing scheduler RM web UI when Node Labels are configured Key: YARN-4391 URL: https://issues.apache.org/jira/browse/YARN-4391 Project:

[jira] [Updated] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3862: --- Summary: Support for fetching specific configs and metrics based on prefixes (was: Decide which

[jira] [Updated] (YARN-4393) TestResourceLocalizationService#testFailedDirsResourceRelease fails intermittently

[ https://issues.apache.org/jira/browse/YARN-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4393: --- Attachment: YARN-4393.01.patch > TestResourceLocalizationService#testFailedDirsResourceRelease fails

[jira] [Updated] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3862: --- Attachment: (was: YARN-3862-YARN-2928.wip.03.patch) > Decide which contents to retrieve and send

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024931#comment-15024931 ] Sunil G commented on YARN-4389: --- One more doubt here, I do not feel we need to deprecate or remove

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024920#comment-15024920 ] Sunil G commented on YARN-4389: --- Yes, +1 for this approach. It make more sense to have this per app level.

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024959#comment-15024959 ] Junping Du commented on YARN-4389: -- Yes. This is what I was thinking and proposing in description. :) >

[jira] [Commented] (YARN-4386) refreshNodesGracefully() looks at active RMNode list for recommissioning decommissioned nodes

[ https://issues.apache.org/jira/browse/YARN-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024968#comment-15024968 ] Hadoop QA commented on YARN-4386: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (YARN-4390) Consider container request size during CS preemption

Eric Payne created YARN-4390: Summary: Consider container request size during CS preemption Key: YARN-4390 URL: https://issues.apache.org/jira/browse/YARN-4390 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4390) Consider container request size during CS preemption

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025044#comment-15025044 ] Eric Payne commented on YARN-4390: -- One approach to alleviate this would be to add a buffer zone around

[jira] [Commented] (YARN-4390) Consider container request size during CS preemption

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025079#comment-15025079 ] Sunil G commented on YARN-4390: --- Hi [~eepayne] Thank you for raising this one. We also ran in to many of this

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024760#comment-15024760 ] Hudson commented on YARN-3980: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2574 (See

[jira] [Commented] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024761#comment-15024761 ] Hudson commented on YARN-4367: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2574 (See

[jira] [Commented] (YARN-4388) Cleanup "mapreduce.job.hdfs-servers" from yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024854#comment-15024854 ] Hadoop QA commented on YARN-4388: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024844#comment-15024844 ] Jason Lowe commented on YARN-4365: -- Thanks for the patch, Kuhu! There appears to be a mix of overriding

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024847#comment-15024847 ] Kuhu Shukla commented on YARN-4365: --- Thanks a lot Jason. Will update revised patch shorty. >

[jira] [Created] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

Junping Du created YARN-4389: Summary: "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster Key: YARN-4389 URL:

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024975#comment-15024975 ] Sunil G commented on YARN-4389: --- I could give a hand here if you haven't started. >

[jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024970#comment-15024970 ] Sunil G commented on YARN-4389: --- Yes, :-) missed the last statement. Thanks for confirming. :-) >

[jira] [Assigned] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster

[ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-4389: - Assignee: Sunil G > "yarn.am.blacklisting.enabled" and >

[jira] [Commented] (YARN-4298) Fix findbugs warnings in hadoop-yarn-common

[ https://issues.apache.org/jira/browse/YARN-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024988#comment-15024988 ] Hudson commented on YARN-4298: -- ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #637 (See

[jira] [Commented] (YARN-4387) Fix typo in FairScheduler log message

[ https://issues.apache.org/jira/browse/YARN-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024987#comment-15024987 ] Hudson commented on YARN-4387: -- ABORTED: Integrated in Hadoop-Hdfs-trunk-Java8 #637 (See

[jira] [Commented] (YARN-4298) Fix findbugs warnings in hadoop-yarn-common

[ https://issues.apache.org/jira/browse/YARN-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024763#comment-15024763 ] Hudson commented on YARN-4298: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2574 (See

[jira] [Commented] (YARN-4380) TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently on branch-2.8

[ https://issues.apache.org/jira/browse/YARN-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15024872#comment-15024872 ] Varun Saxena commented on YARN-4380: [~ozawa], checked the test failure. This issue is coming because

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025820#comment-15025820 ] Wangda Tan commented on YARN-4384: -- +1, committing... > updateNodeResource CLI should not accept negative

[jira] [Updated] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4392: Attachment: YARN-4392.1.patch > ApplicationCreatedEvent event time resets after RM restart/failover >

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025834#comment-15025834 ] Xuan Gong commented on YARN-4392: - Created two patch to fix this issue: 1) the patch with timestamp: when

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025838#comment-15025838 ] Xuan Gong commented on YARN-4392: - + [~jianhe] > ApplicationCreatedEvent event time resets after RM

[jira] [Commented] (YARN-4343) Need to support Application History Server on ATSV2

[ https://issues.apache.org/jira/browse/YARN-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025839#comment-15025839 ] Naganarasimha G R commented on YARN-4343: - Oops, you are right [~sjlee0], after you mentioned i

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

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

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

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

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025852#comment-15025852 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #728 (See

[jira] [Commented] (YARN-4248) REST API for submit/update/delete Reservations

[ https://issues.apache.org/jira/browse/YARN-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025863#comment-15025863 ] Carlo Curino commented on YARN-4248: [~chris.douglas] thanks for the review. I will address your

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025866#comment-15025866 ] Naganarasimha G R commented on YARN-4392: - Hi [~xgong], I prefer not to resend the events on

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025892#comment-15025892 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2660 (See

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025891#comment-15025891 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2660 (See

[jira] [Commented] (YARN-4390) Consider container request size during CS preemption

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025893#comment-15025893 ] Wangda Tan commented on YARN-4390: -- As mentioned by [~sunilg], I think YARN-4108 could be one solution to

[jira] [Commented] (YARN-4391) Exception is logged while accessing scheduler RM web UI when Node Labels are configured

[ https://issues.apache.org/jira/browse/YARN-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025894#comment-15025894 ] Naganarasimha G R commented on YARN-4391: - Hi [~sunilg], I think there is already a defect raised

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025913#comment-15025913 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #719 (See

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025919#comment-15025919 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1451 (See

[jira] [Commented] (YARN-4334) Ability to avoid ResourceManager recovery if state store is "too old"

[ https://issues.apache.org/jira/browse/YARN-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025990#comment-15025990 ] Hadoop QA commented on YARN-4334: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4391) Exception is logged while accessing scheduler RM web UI when Node Labels are configured

[ https://issues.apache.org/jira/browse/YARN-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025993#comment-15025993 ] Bibin A Chundatt commented on YARN-4391: Thanks [~Naganarasimha] . Its duplicate of YARN-4109 . >

[jira] [Resolved] (YARN-4391) Exception is logged while accessing scheduler RM web UI when Node Labels are configured

[ https://issues.apache.org/jira/browse/YARN-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-4391. --- Resolution: Duplicate Thank you for pointing out. Closing this one and will track the issue in YARN-4109 >

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025915#comment-15025915 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #719 (See

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025921#comment-15025921 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1451 (See

[jira] [Commented] (YARN-3769) Consider user limit when calculating total pending resource for preemption policy in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026050#comment-15026050 ] Sangjin Lee commented on YARN-3769: --- [~eepayne], [~leftnoteasy], should this be backported to 2.6.x? >

[jira] [Commented] (YARN-3849) Too much of preemption activity causing continuos killing of containers across queues

[ https://issues.apache.org/jira/browse/YARN-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026053#comment-15026053 ] Sangjin Lee commented on YARN-3849: --- [~sunilg], [~leftnoteasy], does this apply to 2.6.x as well? Should

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026070#comment-15026070 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #729 (See

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026068#comment-15026068 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #729 (See

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026086#comment-15026086 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2661 (See

[jira] [Commented] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026096#comment-15026096 ] Varun Saxena commented on YARN-3862: [~sjlee0], regarding ColumnPrefix.getColumnPrefixBytes(), I had

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026139#comment-15026139 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2577 (See

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026143#comment-15026143 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2577 (See

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026144#comment-15026144 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2577 (See

[jira] [Created] (YARN-4393) TestResourceLocalizationService#testFailedDirsResourceRelease fails intermittently

Varun Saxena created YARN-4393: -- Summary: TestResourceLocalizationService#testFailedDirsResourceRelease fails intermittently Key: YARN-4393 URL: https://issues.apache.org/jira/browse/YARN-4393 Project:

[jira] [Commented] (YARN-4380) TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently on branch-2.8

[ https://issues.apache.org/jira/browse/YARN-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026151#comment-15026151 ] Varun Saxena commented on YARN-4380: [~ozawa], I have filed YARN-4393 for above test case failure >

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026159#comment-15026159 ] Naganarasimha G R commented on YARN-4304: - Hi Sunil, Thanks for working on this patch ! Few

[jira] [Updated] (YARN-2882) Introducing container types

[ https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-2882: - Attachment: YARN-2882-yarn-2877.001.patch I am uploading a new version of the

[jira] [Updated] (YARN-4380) TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently

[ https://issues.apache.org/jira/browse/YARN-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4380: --- Summary: TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently

[jira] [Commented] (YARN-4380) TestResourceLocalizationService.testDownloadingResourcesOnContainerKill fails intermittently

[ https://issues.apache.org/jira/browse/YARN-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026167#comment-15026167 ] Varun Saxena commented on YARN-4380: Changed the JIRA title because this test can potentially fail

[jira] [Commented] (YARN-4384) updateNodeResource CLI should not accept negative values for resource

[ https://issues.apache.org/jira/browse/YARN-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026193#comment-15026193 ] Hudson commented on YARN-4384: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #640 (See

[jira] [Commented] (YARN-4365) FileSystemNodeLabelStore should check for root dir existence on startup

[ https://issues.apache.org/jira/browse/YARN-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026198#comment-15026198 ] Hudson commented on YARN-4365: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #640 (See

[jira] [Commented] (YARN-4132) Separate configs for nodemanager to resourcemanager connection timeout and retries

[ https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026199#comment-15026199 ] Hudson commented on YARN-4132: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #640 (See

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026206#comment-15026206 ] Sunil G commented on YARN-4304: --- Thanks Naga for the comments. bq. 1.In the web page Max application(AM)

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4304: -- Attachment: 0003-YARN-4304.patch Updating new patch addressing findbugs/checkstyle issues. Also had an offline

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026231#comment-15026231 ] Naganarasimha G R commented on YARN-4304: - Thanks for the quick response [~sunilg] bq. Scheduler UI

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026236#comment-15026236 ] Sunil G commented on YARN-4304: --- Thank you for the comments. bq. No, actually if you see we represent queue

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026241#comment-15026241 ] Sunil G commented on YARN-4304: --- Thank you for the comments. Sorry for the partial reply earlier. bq. No,

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026266#comment-15026266 ] Naganarasimha G R commented on YARN-4304: - Hi [~sunilg], bq. As needed I feel it can be handled in

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026270#comment-15026270 ] Hadoop QA commented on YARN-4392: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026285#comment-15026285 ] Sunil G commented on YARN-4304: --- I understand the ordering readability in xml format. So a common class like

  1   2   >