[jira] [Updated] (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 updated YARN-4389: -- Attachment: 0008-YARN-4389.patch Thanks [~rohithsharma] This suggestion makes sense to me. With this, we will

[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=15098246#comment-15098246 ] Sunil G commented on YARN-4389: --- [~djp] and [~rohithsharma], could you please help to check the patch. >

[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=15098292#comment-15098292 ] Sunil G commented on YARN-4389: --- Yes [~djp], that's perfectly fine. We could do that, and I will make

[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=15098285#comment-15098285 ] Junping Du commented on YARN-4389: -- Thanks [~sunilg] for updating the patch. The patch looks pretty good

[jira] [Updated] (YARN-3446) FairScheduler headroom calculation should exclude nodes in the blacklist

[ https://issues.apache.org/jira/browse/YARN-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3446: --- Summary: FairScheduler headroom calculation should exclude nodes in the blacklist (was:

[jira] [Commented] (YARN-4371) "yarn application -kill" should take multiple application ids

[ https://issues.apache.org/jira/browse/YARN-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098447#comment-15098447 ] Sunil G commented on YARN-4371: --- javadoc warning is valid. I will update a new patch. > "yarn application

[jira] [Commented] (YARN-3102) Decommisioned Nodes not listed in Web UI

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

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098511#comment-15098511 ] Karthik Kambatla commented on YARN-1011: [~nroberts], [~leftnoteasy] - reasonable concerns. I am

[jira] [Updated] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

[ https://issues.apache.org/jira/browse/YARN-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4265: Attachment: YARN-4265-trunk.008.patch New patch to address the checkstyle hidden field warning. I also tested

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098502#comment-15098502 ] Naganarasimha G R commented on YARN-3215: - Thanks for detailing out [~sunilg] and small correction

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098525#comment-15098525 ] Kishore Chaliparambil commented on YARN-2885: - Hi [~asuresh], I am reviewing the latest patch.

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098526#comment-15098526 ] Sunil G commented on YARN-4108: --- Thank you [~leftnoteasy] for the detailed updated design doc. Few comments

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098461#comment-15098461 ] Xuan Gong commented on YARN-4577: - Thanks, [~sjlee0] for the comments and suggestions. +1 for the

[jira] [Commented] (YARN-4512) Provide a knob to turn on over-allocation

[ https://issues.apache.org/jira/browse/YARN-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097781#comment-15097781 ] Inigo Goiri commented on YARN-4512: --- bq. I'm not very familiar with ResourceOption, is it only used by

[jira] [Updated] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4538: --- Attachment: 0004-YARN-4538.patch Attaching updated patch > QueueMetrics pending cores and

[jira] [Updated] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4584: --- Summary: RM startup failure when AM attempts greater than max-attempts (was: RM start failure

[jira] [Updated] (YARN-4462) FairScheduler: Disallow preemption from a queue

[ https://issues.apache.org/jira/browse/YARN-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Jie updated YARN-4462: -- Attachment: YARN-4462.004.patch > FairScheduler: Disallow preemption from a queue >

[jira] [Commented] (YARN-4553) Add cgroups support for docker containers

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

[jira] [Commented] (YARN-4462) FairScheduler: Disallow preemption from a queue

[ https://issues.apache.org/jira/browse/YARN-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097879#comment-15097879 ] Tao Jie commented on YARN-4462: --- [~kasha] , Thank you for your comments. I will make some improvements as you

[jira] [Commented] (YARN-3446) FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

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

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097913#comment-15097913 ] Bibin A Chundatt commented on YARN-4538: [~leftnoteasy] Thank you for review . Attached patch based

[jira] [Commented] (YARN-4534) Remove the redundant symbol in yarn rmadmin help msg

[ https://issues.apache.org/jira/browse/YARN-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097936#comment-15097936 ] Lin Yiqun commented on YARN-4534: - Thanks [~ajisakaa] for review and commit! > Remove the redundant symbol

[jira] [Updated] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4584: --- Attachment: 0001-YARN-4584.patch > RM startup failure when AM attempts greater than

[jira] [Commented] (YARN-4462) FairScheduler: Disallow preemption from a queue

[ https://issues.apache.org/jira/browse/YARN-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097957#comment-15097957 ] Tao Jie commented on YARN-4462: --- Updates： 1, Rename config in fair-scheduler.xml from ** to *false* 2,

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097958#comment-15097958 ] Bibin A Chundatt commented on YARN-4584: [~rohithsharma] Thank you for looking into the issue . As

[jira] [Updated] (YARN-4317) Test failure: TestResourceTrackerService

[ https://issues.apache.org/jira/browse/YARN-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4317: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4478 > Test failure:

[jira] [Updated] (YARN-4453) TestMiniYarnClusterNodeUtilization occasionally times out in trunk

[ https://issues.apache.org/jira/browse/YARN-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4453: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4478 >

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098076#comment-15098076 ] Bibin A Chundatt commented on YARN-4584: [~rohithsharma] Testcase failures are not related to patch

[jira] [Commented] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098085#comment-15098085 ] Sunil G commented on YARN-2009: --- Thanks [~leftnoteasy] for sharing the updates. I will also take a look on

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

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

[jira] [Updated] (YARN-3568) TestAMRMTokens should use some random port

[ https://issues.apache.org/jira/browse/YARN-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3568: --- Issue Type: Sub-task (was: Bug) Parent: YARN-4478 > TestAMRMTokens should use some

[jira] [Commented] (YARN-4565) When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only

[ https://issues.apache.org/jira/browse/YARN-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098034#comment-15098034 ] Naganarasimha G R commented on YARN-4565: - +1, Patch LGTM > When sizeBasedWeight enabled for

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

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

[jira] [Commented] (YARN-4462) FairScheduler: Disallow preemption from a queue

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

[jira] [Commented] (YARN-4590) SLS(Scheduler Load Simulator) web pages can't load css and js resource

[ https://issues.apache.org/jira/browse/YARN-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098168#comment-15098168 ] Bibin A Chundatt commented on YARN-4590: [~xupeng] Can you try from {{hadoop/tools/sls}} as below

[jira] [Commented] (YARN-3446) FairScheduler headroom calculation should exclude nodes in the blacklist

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

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098341#comment-15098341 ] Eric Payne commented on YARN-4108: -- bq. Do you have any comments/suggestions about the latest proposal?

[jira] [Commented] (YARN-3446) FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

[ https://issues.apache.org/jira/browse/YARN-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098347#comment-15098347 ] zhihai xu commented on YARN-3446: - The test failures for TestClientRMTokens and TestAMAuthorizatio are not

[jira] [Commented] (YARN-4371) "yarn application -kill" should take multiple application ids

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

[jira] [Commented] (YARN-4565) When sizeBasedWeight enabled for FairOrderingPolicy in CapacityScheduler, Sometimes lead to situation where all queue resources consumed by AMs only

[ https://issues.apache.org/jira/browse/YARN-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101108#comment-15101108 ] Wangda Tan commented on YARN-4565: -- Thanks [~Naganarasimha]! > When sizeBasedWeight enabled for

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101117#comment-15101117 ] Wangda Tan commented on YARN-3215: -- Thanks [~sunilg]/[~Naganarasimha]. bq. min (total unused

[jira] [Created] (YARN-4597) Add SCHEDULE to NM container lifecycle

Chris Douglas created YARN-4597: --- Summary: Add SCHEDULE to NM container lifecycle Key: YARN-4597 URL: https://issues.apache.org/jira/browse/YARN-4597 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4595) Add support for configurable read-only mounts

Billie Rinaldi created YARN-4595: Summary: Add support for configurable read-only mounts Key: YARN-4595 URL: https://issues.apache.org/jira/browse/YARN-4595 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

[ https://issues.apache.org/jira/browse/YARN-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4428: --- Attachment: YARN-4428.3.patch > Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

[jira] [Commented] (YARN-4496) Improve HA ResourceManager Failover detection on the client

[ https://issues.apache.org/jira/browse/YARN-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101053#comment-15101053 ] Jian He commented on YARN-4496: --- taking over, thanks ! > Improve HA ResourceManager Failover detection on

[jira] [Assigned] (YARN-4496) Improve HA ResourceManager Failover detection on the client

[ https://issues.apache.org/jira/browse/YARN-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-4496: - Assignee: Jian He (was: Arun Suresh) > Improve HA ResourceManager Failover detection on the client >

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101115#comment-15101115 ] Wangda Tan commented on YARN-4538: -- +1 to latest patch, [~bibinchundatt], could you take a look at

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101106#comment-15101106 ] Wangda Tan commented on YARN-1011: -- bq. Welcome any thoughts/suggestions on handling promotion if we allow

[jira] [Commented] (YARN-4512) Provide a knob to turn on over-allocation

[ https://issues.apache.org/jira/browse/YARN-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101110#comment-15101110 ] Wangda Tan commented on YARN-4512: -- Thanks [~elgoiri], I don't have strong opinion regarding to use

[jira] [Created] (YARN-4596) SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities

Li Lu created YARN-4596: --- Summary: SystemMetricPublisher should not swallow error messages from TimelineClient#putEntities Key: YARN-4596 URL: https://issues.apache.org/jira/browse/YARN-4596 Project: Hadoop

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101143#comment-15101143 ] Wangda Tan commented on YARN-4108: -- Hi [~sunilg] bq. 1. In current PCPP, we first preempt all reserved

[jira] [Commented] (YARN-4597) Add SCHEDULE to NM container lifecycle

[ https://issues.apache.org/jira/browse/YARN-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101149#comment-15101149 ] Chris Douglas commented on YARN-4597: - The {{ContainerLaunchContext}} (CLC) specifies the prerequisites

[jira] [Commented] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

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

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

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

[jira] [Commented] (YARN-4592) Remove unsed GetContainerStatus proto

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

[jira] [Updated] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4559: -- Attachment: YARN-4559.2.patch > Make leader elector and zk store share the same curator client >

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

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

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099154#comment-15099154 ] Karthik Kambatla commented on YARN-4559: bq. I think the best way is just to merge the

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099163#comment-15099163 ] Jian He commented on YARN-4559: --- bq. ZK-leader election with a different store. I think currently only

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099185#comment-15099185 ] Karthik Kambatla commented on YARN-4559: There "could" be other stores that provide the same

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099088#comment-15099088 ] Eric Payne commented on YARN-4108: -- [~leftnoteasy], great job! This approach looks like it has potential

[jira] [Updated] (YARN-4589) Diagnostics for localization timeouts is lacking

[ https://issues.apache.org/jira/browse/YARN-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4589: --- Attachment: YARN-4589.2.patch > Diagnostics for localization timeouts is lacking >

[jira] [Commented] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099068#comment-15099068 ] Jian He commented on YARN-4559: --- new patch moved the curator#close in RM#serviceStop. I cannot move the

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

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

[jira] [Commented] (YARN-4594) Fix test-container-executor.c to pass

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

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099209#comment-15099209 ] Bibin A Chundatt commented on YARN-4584: [~jianhe] The AM is getting pre-empted and exceeds the max

[jira] [Commented] (YARN-4551) Address the duplication between StatusUpdateWhenHealthy and StatusUpdateWhenUnhealthy transitions

[ https://issues.apache.org/jira/browse/YARN-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098574#comment-15098574 ] Sunil G commented on YARN-4551: --- Thank you [~kasha] for the review and commit! > Address the duplication

[jira] [Commented] (YARN-3102) Decommisioned Nodes not listed in Web UI

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

[jira] [Commented] (YARN-4558) Yarn client retries on some non-retriable exceptions

[ https://issues.apache.org/jira/browse/YARN-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098722#comment-15098722 ] Sergey Shelukhin commented on YARN-4558: In this case, retry policy is built in YARN code. I don't

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098556#comment-15098556 ] Steve Loughran commented on YARN-4577: -- Test wise * {{testLoadAuxServiceLocally}} should be calling

[jira] [Commented] (YARN-4589) Diagnostics for localization timeouts is lacking

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

[jira] [Commented] (YARN-4502) Sometimes Two AM containers get launched

Assignee: Vinod Kumar Vavilapalli >Priority: Critical > Attachments: YARN-4502-20160114.txt, YARN-4502-20160212.txt > > > Scenario : > * set yarn.resourcemanager.am.max-attempts = 2 > * start dshell application > {code} > yarn org.apache.hadoop.yarn.ap

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101166#comment-15101166 ] Wangda Tan commented on YARN-4108: -- Thanks for looking at this, [~eepayne]. bq. In the lazy preemption

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101222#comment-15101222 ] Rohith Sharma K S commented on YARN-4584: - I had offline discussion with [~jianhe] regarding this

[jira] [Created] (YARN-4598) Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL

tangshangwen created YARN-4598: -- Summary: Invalid event: RESOURCE_FAILED at CONTAINER_CLEANEDUP_AFTER_KILL Key: YARN-4598 URL: https://issues.apache.org/jira/browse/YARN-4598 Project: Hadoop YARN

[jira] [Updated] (YARN-4502) Sometimes Two AM containers get launched

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-4502: -- Attachment: YARN-4502-20160114.txt Tx for the review, [~leftnoteasy] bq. Do you

[jira] [Updated] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4538: --- Attachment: 0005-YARN-4538.patch [~leftnoteasy] Thanks for review . Sorry to miss javadoc.

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15099191#comment-15099191 ] Sangjin Lee commented on YARN-4577: --- {quote} The use case here is simple: if we specify the aux-services

[jira] [Commented] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

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

[jira] [Updated] (YARN-4559) Make leader elector and zk store share the same curator client

[ https://issues.apache.org/jira/browse/YARN-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4559: -- Attachment: YARN-4559.3.patch > Make leader elector and zk store share the same curator client >

[jira] [Updated] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3998: --- Attachment: YARN-3998.03.patch > Add retry-times to let NM re-launch container when it fails to run >

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101383#comment-15101383 ] Jun Gong commented on YARN-3998: [~vvasudev] Thanks for the detailed review and suggestions! I just

[jira] [Updated] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3998: --- Attachment: YARN-3998.04.patch Sorry, there is something wrong with YARN-3998.03.patch. Attached a new patch

[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=15098785#comment-15098785 ] Hadoop QA commented on YARN-4389: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (YARN-4593) Deadlock in AbstractService.getConfig()

Steve Loughran created YARN-4593: Summary: Deadlock in AbstractService.getConfig() Key: YARN-4593 URL: https://issues.apache.org/jira/browse/YARN-4593 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098825#comment-15098825 ] Steve Loughran commented on YARN-4593: -- I don't see why we need this to be synchronized (it's that way

[jira] [Commented] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098826#comment-15098826 ] Steve Loughran commented on YARN-4593: -- SLIDER-1052 shows this. I'm not going to blame this JIRA for

[jira] [Updated] (YARN-4593) Deadlock in AbstractService.getConfig()

[ https://issues.apache.org/jira/browse/YARN-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4593: - Attachment: YARN-4593-001.patch Patch 001, removes the -synchronized attributed. The field is

[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=15098583#comment-15098583 ] Hadoop QA commented on YARN-4389: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-3446) FairScheduler headroom calculation should exclude nodes in the blacklist

[ https://issues.apache.org/jira/browse/YARN-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098617#comment-15098617 ] zhihai xu commented on YARN-3446: - [~kasha], thanks for the review and committing the patch! >

[jira] [Updated] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4311: -- Attachment: YARN-4311-v8.patch Thank you [~jlowe] for the review comments. I have updated the patch. The

[jira] [Created] (YARN-4592) Remove unsed GetContainerStatus proto

Chang Li created YARN-4592: -- Summary: Remove unsed GetContainerStatus proto Key: YARN-4592 URL: https://issues.apache.org/jira/browse/YARN-4592 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-4592) Remove unsed GetContainerStatus proto

[ https://issues.apache.org/jira/browse/YARN-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4592: --- Attachment: YARN-4592.patch > Remove unsed GetContainerStatus proto > - >

[jira] [Updated] (YARN-4428) Redirect RM page to AHS page when AHS turned on and RM page is not avaialable

[ https://issues.apache.org/jira/browse/YARN-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4428: --- Attachment: YARN-4428.3.patch thanks [~jlowe] for review and point me to the related issue! updated .3 patch

[jira] [Updated] (YARN-4371) "yarn application -kill" should take multiple application ids

[ https://issues.apache.org/jira/browse/YARN-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4371: -- Attachment: 0006-YARN-4371.patch Fixing javadoc issue. > "yarn application -kill" should take multiple

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098641#comment-15098641 ] Giovanni Matteo Fumarola commented on YARN-2885: Agree with [~kishorch]. If it will remain

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098219#comment-15098219 ] Sunil G commented on YARN-3215: --- Hi [~Naganarasimha Garla] As discussed offline, I will try explaining the

[jira] [Updated] (YARN-4371) "yarn application -kill" should take multiple application ids

[ https://issues.apache.org/jira/browse/YARN-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4371: -- Attachment: 0005-YARN-4371.patch Thank you [~jlowe] for the comments. I have updated the patch as per same. >

[jira] [Commented] (YARN-3542) Re-factor support for CPU as a resource using the new ResourceHandler mechanism

[ https://issues.apache.org/jira/browse/YARN-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15098214#comment-15098214 ] Varun Vasudev commented on YARN-3542: - {quote} This effectively means the old code is not used

[jira] [Updated] (YARN-3102) Decommisioned Nodes not listed in Web UI

[ https://issues.apache.org/jira/browse/YARN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-3102: -- Attachment: YARN-3102-v5.patch Addressed findbugs warning. > Decommisioned Nodes not listed in Web UI >

  1   2   >