[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458695#comment-15458695 ] Eric Payne commented on YARN-4945: -- [~sunilg], just one quick note: I am getting a

[jira] [Commented] (YARN-5549) AMLauncher.createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458504#comment-15458504 ] Daniel Templeton commented on YARN-5549: Minor correction, [~Naganarasimha]: it requires a restart

[jira] [Updated] (YARN-5595) Update documentation and Javadoc to match change to NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5595: --- Attachment: YARN-5595.001.patch > Update documentation and Javadoc to match change to >

[jira] [Updated] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5549: - Summary: AMLauncher#createAMContainerLaunchContext() should not log the command to be launched

[jira] [Commented] (YARN-5617) AMs only intended to run one attempt can be run more than once

[ https://issues.apache.org/jira/browse/YARN-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459242#comment-15459242 ] Jason Lowe commented on YARN-5617: -- See TEZ-3426 for an example of an app framework that was depending

[jira] [Comment Edited] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459234#comment-15459234 ] Daniel Templeton edited comment on YARN-5608 at 9/2/16 6:23 PM: Thanks,

[jira] [Updated] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5608: --- Attachment: YARN-5608.005.patch Thanks, [~rohithsharma]. Much better to use the built-in

[jira] [Updated] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5608: --- Attachment: YARN-5608.005.patch > TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[jira] [Commented] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459266#comment-15459266 ] Hudson commented on YARN-5549: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10392 (See

[jira] [Created] (YARN-5616) Clean up WeightAdjuster

Yufei Gu created YARN-5616: -- Summary: Clean up WeightAdjuster Key: YARN-5616 URL: https://issues.apache.org/jira/browse/YARN-5616 Project: Hadoop YARN Issue Type: Improvement Components:

[jira] [Created] (YARN-5617) AMs only intended to run one attempt can be run more than once

Jason Lowe created YARN-5617: Summary: AMs only intended to run one attempt can be run more than once Key: YARN-5617 URL: https://issues.apache.org/jira/browse/YARN-5617 Project: Hadoop YARN

[jira] [Commented] (YARN-5595) Update documentation and Javadoc to match change to NodeHealthScriptRunner#reportHealthStatus

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

[jira] [Updated] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5608: --- Attachment: (was: YARN-5608.005.patch) > TestAMRMClient.setup() fails with

[jira] [Commented] (YARN-5617) AMs only intended to run one attempt can be run more than once

[ https://issues.apache.org/jira/browse/YARN-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459619#comment-15459619 ] Giovanni Matteo Fumarola commented on YARN-5617: +1, thanks [~jlowe] for the JIRA. This

[jira] [Commented] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

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

[jira] [Commented] (YARN-5601) Make the RM epoch base value configurable

[ https://issues.apache.org/jira/browse/YARN-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459370#comment-15459370 ] Subru Krishnan commented on YARN-5601: -- Thanks [~jianhe] for reviewing/committing. > Make the RM

[jira] [Commented] (YARN-4205) Add a service for monitoring application life time out

[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459472#comment-15459472 ] Vinod Kumar Vavilapalli commented on YARN-4205: --- This looks good in general. As discussed on

[jira] [Updated] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5549: --- Target Version/s: 2.8.0 I actually think we should push this into the next release (2.8) as

[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels

[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459352#comment-15459352 ] Naganarasimha G R commented on YARN-4855: - Hi [~Tao Jie], Sorry for the really long delay in

[jira] [Updated] (YARN-5616) Clean up WeightAdjuster

[ https://issues.apache.org/jira/browse/YARN-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5616: --- Description: {{WeightAdjuster}} and its implementation {{NewAppWeightBooster}} are never used. We should

[jira] [Reopened] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang reopened YARN-5549: -- Re-openeing until I push through to branch-2.8. [~templedf], please provide a branch-2/branch-2.8 patch

[jira] [Updated] (YARN-5555) Scheduler UI: "% of Queue" is inaccurate if leaf queue is hierarchically nested.

[ https://issues.apache.org/jira/browse/YARN-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated YARN-: -- Fix Version/s: 3.0.0-alpha2 > Scheduler UI: "% of Queue" is inaccurate if leaf queue is hierarchically

[jira] [Commented] (YARN-5596) Fix failing unit test in TestDockerContainerRuntime

[ https://issues.apache.org/jira/browse/YARN-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459673#comment-15459673 ] Andrew Wang commented on YARN-5596: --- Gentle reminder to please include the appropriate 3.0.0 fix version

[jira] [Resolved] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang resolved YARN-5549. -- Resolution: Fixed Fix Version/s: (was: 3.0.0-alpha2) 2.8.0 Pushed to

[jira] [Commented] (YARN-5264) Store all queue-specific information in FSQueue

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459746#comment-15459746 ] Hudson commented on YARN-5264: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10393 (See

[jira] [Commented] (YARN-5616) Clean up WeightAdjuster

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

[jira] [Updated] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5549: --- Attachment: YARN-5549.branch-2.001.patch > AMLauncher#createAMContainerLaunchContext() should

[jira] [Comment Edited] (YARN-5549) AMLauncher#createAMContainerLaunchContext() should not log the command to be launched indiscriminately

[ https://issues.apache.org/jira/browse/YARN-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459590#comment-15459590 ] Ray Chiang edited comment on YARN-5549 at 9/2/16 10:02 PM: --- Re-opening until I

[jira] [Commented] (YARN-5486) Update OpportunisticContainerAllocatorAMService::allocate method to handle OPPORTUNISTIC container requests

[ https://issues.apache.org/jira/browse/YARN-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459847#comment-15459847 ] Subru Krishnan commented on YARN-5486: -- Thanks [~asuresh] for the patch. I looked at it and have a few

[jira] [Commented] (YARN-5264) Use FSQueue to store queue-specific information

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459690#comment-15459690 ] Karthik Kambatla commented on YARN-5264: +1. Committing this. > Use FSQueue to store

[jira] [Commented] (YARN-1072) Need a default NodeManager health check script

[ https://issues.apache.org/jira/browse/YARN-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459703#comment-15459703 ] Yufei Gu commented on YARN-1072: Agree with [~aw], It is not necessary to provide a default NM health check

[jira] [Comment Edited] (YARN-1072) Need a default NodeManager health check script

[ https://issues.apache.org/jira/browse/YARN-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459703#comment-15459703 ] Yufei Gu edited comment on YARN-1072 at 9/2/16 9:59 PM: Agree with [~aw], It is not

[jira] [Resolved] (YARN-1072) Need a default NodeManager health check script

[ https://issues.apache.org/jira/browse/YARN-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu resolved YARN-1072. Resolution: Won't Fix > Need a default NodeManager health check script >

[jira] [Commented] (YARN-5264) Store all queue-specific information in FSQueue

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459723#comment-15459723 ] Yufei Gu commented on YARN-5264: Thanks [~kasha] for the review and checking this in. Thanks [~templedf]

[jira] [Updated] (YARN-5616) Clean up WeightAdjuster

[ https://issues.apache.org/jira/browse/YARN-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5616: --- Attachment: YARN-5616.001.patch > Clean up WeightAdjuster > --- > > Key:

[jira] [Updated] (YARN-5616) Clean up WeightAdjuster

[ https://issues.apache.org/jira/browse/YARN-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5616: --- Description: {{WeightAdjuster}} and its implementation {{NewAppWeightBooster}} are never used. We should

[jira] [Updated] (YARN-5596) Fix failing unit test in TestDockerContainerRuntime

[ https://issues.apache.org/jira/browse/YARN-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated YARN-5596: -- Fix Version/s: 3.0.0-alpha2 > Fix failing unit test in TestDockerContainerRuntime >

[jira] [Updated] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated YARN-5221: -- Fix Version/s: 3.0.0-alpha2 2.8.0 > Expose UpdateResourceRequest API to allow AM to

[jira] [Commented] (YARN-5221) Expose UpdateResourceRequest API to allow AM to request for change in container properties

[ https://issues.apache.org/jira/browse/YARN-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459680#comment-15459680 ] Andrew Wang commented on YARN-5221: --- Gentle reminder to please include the appropriate 3.0.0 fix version

[jira] [Updated] (YARN-5264) Store all queue-specific information in FSQueue

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5264: --- Summary: Store all queue-specific information in FSQueue (was: Use FSQueue to store

[jira] [Created] (YARN-5615) NMClienAsynct#CallbackHandler#onContainerStarted/Stopped does not necessarily mean container started/stopped

Jian He created YARN-5615: - Summary: NMClienAsynct#CallbackHandler#onContainerStarted/Stopped does not necessarily mean container started/stopped Key: YARN-5615 URL: https://issues.apache.org/jira/browse/YARN-5615

[jira] [Commented] (YARN-5614) NMClient APIs do not need to take NodeId

[ https://issues.apache.org/jira/browse/YARN-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457924#comment-15457924 ] Ying Zhang commented on YARN-5614: -- Sounds reasonable. > NMClient APIs do not need to take NodeId >

[jira] [Updated] (YARN-5615) onContainerStarted/Stopped callback handler in NMClientAsync does not necessarily mean container started/stopped

[ https://issues.apache.org/jira/browse/YARN-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5615: -- Summary: onContainerStarted/Stopped callback handler in NMClientAsync does not necessarily mean container

[jira] [Commented] (YARN-5608) TestAMRMClient.setup() fails with ArrayOutOfBoundsException

[ https://issues.apache.org/jira/browse/YARN-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458000#comment-15458000 ] Rohith Sharma K S commented on YARN-5608: - The current patch wait for NodeManager to register in

[jira] [Commented] (YARN-5615) onContainerStarted/Stopped callback handler in NMClientAsync does not necessarily mean container started/stopped

[ https://issues.apache.org/jira/browse/YARN-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457917#comment-15457917 ] Jian He commented on YARN-5615: --- HADOOP-11552 is one solution to this. NMClient waits until the container is

[jira] [Commented] (YARN-5576) Core change to localize resource while container is running

[ https://issues.apache.org/jira/browse/YARN-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458006#comment-15458006 ] Varun Vasudev commented on YARN-5576: - [~asuresh] - can I go ahead and commit the latest patch? > Core

[jira] [Commented] (YARN-5552) Add Builder methods for common yarn API records

[ https://issues.apache.org/jira/browse/YARN-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457799#comment-15457799 ] Tao Jie commented on YARN-5552: --- Failed testcase passed in my local environment. > Add Builder methods for

[jira] [Updated] (YARN-5614) NMClient APIs do not need to take NodeId

[ https://issues.apache.org/jira/browse/YARN-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-5614: -- Description: Currently, all the NMClient APIs, e.g. startContainer, stopContainer, getContainerStatus force

[jira] [Commented] (YARN-5614) NMClient APIs do not need to take NodeId

[ https://issues.apache.org/jira/browse/YARN-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457793#comment-15457793 ] Jian He commented on YARN-5614: --- Actually, this may not be that straightfoward.. if the cache in NMClient is

[jira] [Commented] (YARN-5576) Core change to localize resource while container is running

[ https://issues.apache.org/jira/browse/YARN-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457665#comment-15457665 ] Arun Suresh commented on YARN-5576: --- bq. the method in ContainerManagerImpl only allows localization

[jira] [Created] (YARN-5614) NMClient APIs do not need to take NodeId

Jian He created YARN-5614: - Summary: NMClient APIs do not need to take NodeId Key: YARN-5614 URL: https://issues.apache.org/jira/browse/YARN-5614 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-5428) Allow for specifying the docker client configuration directory

[ https://issues.apache.org/jira/browse/YARN-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458335#comment-15458335 ] Shane Kumpf commented on YARN-5428: --- Thanks for the review [~tangzhankun]! Yes, we will need to

[jira] [Commented] (YARN-5555) Scheduler UI: "% of Queue" is inaccurate if leaf queue is hierarchically nested.

[ https://issues.apache.org/jira/browse/YARN-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458223#comment-15458223 ] Hudson commented on YARN-: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10389 (See