[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784719#comment-15784719 ] Bibin A Chundatt commented on YARN-6031: [~templedf] {quote} so that when using

[jira] [Commented] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784442#comment-15784442 ] Junping Du commented on YARN-5709: -- Interesting...Why these javadoc warnings only against jdk v1.8? >

[jira] [Commented] (YARN-4090) Make Collections.sort() more efficient in FSParentQueue.java

[ https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784417#comment-15784417 ] zhangshilong commented on YARN-4090: would you please tell me yarn version you used? In trunk:

[jira] [Commented] (YARN-4090) Make Collections.sort() more efficient in FSParentQueue.java

[ https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784392#comment-15784392 ] zhangshilong commented on YARN-4090: [~xinxianyin] [~yufeigu] This optimization works in our

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784388#comment-15784388 ] Tao Yang commented on YARN-6029: Thanks [~wangda]. Updated priority to Critical and Attached new patch for

[jira] [Updated] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved co

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-6029: --- Attachment: YARN-6029.002.patch > CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784349#comment-15784349 ] Ying Zhang edited comment on YARN-6031 at 12/29/16 3:03 AM: {quote} Do you

[jira] [Updated] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved co

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tao Yang updated YARN-6029: --- Priority: Critical (was: Blocker) > CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784349#comment-15784349 ] Ying Zhang edited comment on YARN-6031 at 12/29/16 3:00 AM: {quote} Do you

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784349#comment-15784349 ] Ying Zhang commented on YARN-6031: -- {quote} Do you think we can make the log message a bit more explicit,

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784332#comment-15784332 ] Ying Zhang commented on YARN-6031: -- So what's the next move? I'm a little confused. Are we going to

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784327#comment-15784327 ] Ying Zhang commented on YARN-6031: -- {quote} We could ignore/reset labels to default in resourcerequest

[jira] [Commented] (YARN-5685) Non-embedded HA failover is broken

[ https://issues.apache.org/jira/browse/YARN-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784191#comment-15784191 ] Karthik Kambatla commented on YARN-5685: On YARN-5709, Jian made the point that it is unlikely we

[jira] [Commented] (YARN-5709) Cleanup leader election configs and pluggability

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

[jira] [Updated] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5830: --- Attachment: YARN-5830.002.patch [~kasha], uploaded the new patch for all your comments. YARN-6038 is created

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784103#comment-15784103 ] Wangda Tan commented on YARN-6029: -- And in addition, I suggest to downgrade severity to critical to

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784099#comment-15784099 ] Wangda Tan commented on YARN-6029: -- bq. I'm not clear about this. Is it worth to ensure consistency of

[jira] [Commented] (YARN-5685) Non-embedded HA failover is broken

[ https://issues.apache.org/jira/browse/YARN-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784070#comment-15784070 ] Daniel Templeton commented on YARN-5685: I would look at it the other way around. The default

[jira] [Comment Edited] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784024#comment-15784024 ] Yufei Gu edited comment on YARN-5830 at 12/28/16 11:58 PM: --- [~kasha], thanks for

[jira] [Commented] (YARN-5556) Support for deleting queues without requiring a RM restart

[ https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784035#comment-15784035 ] Naganarasimha Garla commented on YARN-5556: --- Thanks Xuan, will start working on it and update the

[jira] [Comment Edited] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784024#comment-15784024 ] Yufei Gu edited comment on YARN-5830 at 12/28/16 11:53 PM: --- [~kasha], thanks for

[jira] [Issue Comment Deleted] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5709: --- Comment: was deleted (was: Also, looks to me like this is committed to branch-2, but not

[jira] [Commented] (YARN-5830) Avoid preempting AM containers

[ https://issues.apache.org/jira/browse/YARN-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784024#comment-15784024 ] Yufei Gu commented on YARN-5830: [~kasha], thanks for the review. The high-level approach: 1. In first

[jira] [Commented] (YARN-5556) Support for deleting queues without requiring a RM restart

[ https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784018#comment-15784018 ] Xuan Gong commented on YARN-5556: - [~Naganarasimha] Given all the dependent patches have been committed,

[jira] [Resolved] (YARN-5755) Enhancements to STOP queue handling

[ https://issues.apache.org/jira/browse/YARN-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-5755. - Resolution: Duplicate Fix Version/s: 3.0.0-alpha2 2.9.0 > Enhancements to STOP

[jira] [Commented] (YARN-5755) Enhancements to STOP queue handling

[ https://issues.apache.org/jira/browse/YARN-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784014#comment-15784014 ] Xuan Gong commented on YARN-5755: - Close this as duplicate. The issue has already been handled in YARN-5756

[jira] [Commented] (YARN-5987) NM configured command to collect heap dump of preempted container

[ https://issues.apache.org/jira/browse/YARN-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15784003#comment-15784003 ] Daniel Templeton commented on YARN-5987: Thanks, [~miklos.szeg...@cloudera.com]. Is it possible to

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

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

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783989#comment-15783989 ] Daniel Templeton commented on YARN-4882: Thanks, [~rkanter]! > Change the log level to DEBUG for

[jira] [Commented] (YARN-5258) Document Use of Docker with LinuxContainerExecutor

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

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783961#comment-15783961 ] Robert Kanter commented on YARN-4882: - +1 > Change the log level to DEBUG for recovering completed

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

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

[jira] [Updated] (YARN-6038) Check other resource requests if cannot match the first one while identifying containers to preempt

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6038: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-5990 > Check other resource requests if cannot

[jira] [Updated] (YARN-6038) Check other resource requests if cannot match the first one while identifying containers to preempt

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6038: --- Summary: Check other resource requests if cannot match the first one while identifying containers to preempt

[jira] [Updated] (YARN-6038) Check other resource requests if cannot match the first one while identify containers to preempt

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6038: --- Summary: Check other resource requests if cannot match the first one while identify containers to preempt

[jira] [Updated] (YARN-5258) Document Use of Docker with LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5258: --- Attachment: YARN-5258.004.patch Looks like I missed [~tangzhankun]'s comments before. This

[jira] [Updated] (YARN-6038) Check other resource requests if cannot match the first one

[ https://issues.apache.org/jira/browse/YARN-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6038: --- Summary: Check other resource requests if cannot match the first one (was: Check other resource requests if

[jira] [Commented] (YARN-5849) Automatically create YARN control group for pre-mounted cgroups

[ https://issues.apache.org/jira/browse/YARN-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783916#comment-15783916 ] Daniel Templeton commented on YARN-5849: Latest patch looks good to me. [~bibinchundatt], any

[jira] [Commented] (YARN-5554) MoveApplicationAcrossQueues does not check user permission on the target queue

[ https://issues.apache.org/jira/browse/YARN-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783908#comment-15783908 ] Daniel Templeton commented on YARN-5554: Let's get this thing closed out. A few more comments: *

[jira] [Commented] (YARN-5554) MoveApplicationAcrossQueues does not check user permission on the target queue

[ https://issues.apache.org/jira/browse/YARN-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783850#comment-15783850 ] Daniel Templeton commented on YARN-5554: Yep, I noticed that as well. The {{remoteAddress}} and

[jira] [Updated] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4882: --- Attachment: YARN-4882.005.patch Changed the colon in the attempt message to an equals. >

[jira] [Updated] (YARN-5709) Cleanup leader election configs and pluggability

[ https://issues.apache.org/jira/browse/YARN-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-5709: --- Attachment: yarn-5709-branch-2.8.03.patch Forgot we were talking about branch-2.8, so the

[jira] [Commented] (YARN-5275) Timeline application page cannot be loaded when no application submitted/running on the cluster after HADOOP-9613

[ https://issues.apache.org/jira/browse/YARN-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783754#comment-15783754 ] Daniel Templeton commented on YARN-5275: Ping, [~sunilg]... > Timeline application page cannot be

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783757#comment-15783757 ] Daniel Templeton commented on YARN-2962: No worries. I'm happy to help with the review. >

[jira] [Resolved] (YARN-4401) A failed app recovery should not prevent the RM from starting

[ https://issues.apache.org/jira/browse/YARN-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton resolved YARN-4401. Resolution: Won't Fix This JIRA is superseded by YARN-6035, YARN-6036, and YARN-6037, which

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783546#comment-15783546 ] Daniel Templeton edited comment on YARN-6031 at 12/28/16 7:22 PM: -- bq.

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783546#comment-15783546 ] Daniel Templeton commented on YARN-6031: bq. IIUC ignore validation on recovery also should work.

[jira] [Commented] (YARN-5831) Propagate allowPreemptionFrom flag all the way down to the app

[ https://issues.apache.org/jira/browse/YARN-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783486#comment-15783486 ] Karthik Kambatla commented on YARN-5831: Thanks for working on this, Yufei. Comments on the

[jira] [Created] (YARN-6038) Check other resource requests if we can't match the first one

Yufei Gu created YARN-6038: -- Summary: Check other resource requests if we can't match the first one Key: YARN-6038 URL: https://issues.apache.org/jira/browse/YARN-6038 Project: Hadoop YARN Issue

[jira] [Created] (YARN-6037) Add an option to yarn resourcemanager CLI to list all applications that would cause a recovery failure

Daniel Templeton created YARN-6037: -- Summary: Add an option to yarn resourcemanager CLI to list all applications that would cause a recovery failure Key: YARN-6037 URL:

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783397#comment-15783397 ] Bibin A Chundatt edited comment on YARN-6031 at 12/28/16 6:31 PM: -- As

[jira] [Created] (YARN-6036) Add -show-application-info option to yarn resourcemanager CLI

Daniel Templeton created YARN-6036: -- Summary: Add -show-application-info option to yarn resourcemanager CLI Key: YARN-6036 URL: https://issues.apache.org/jira/browse/YARN-6036 Project: Hadoop YARN

[jira] [Created] (YARN-6035) Add -force-recovery option to yarn resourcemanager

Daniel Templeton created YARN-6035: -- Summary: Add -force-recovery option to yarn resourcemanager Key: YARN-6035 URL: https://issues.apache.org/jira/browse/YARN-6035 Project: Hadoop YARN

[jira] [Assigned] (YARN-5824) Verify app starvation under custom preemption thresholds and timeouts

[ https://issues.apache.org/jira/browse/YARN-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu reassigned YARN-5824: -- Assignee: Yufei Gu > Verify app starvation under custom preemption thresholds and timeouts >

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783397#comment-15783397 ] Bibin A Chundatt edited comment on YARN-6031 at 12/28/16 6:08 PM: -- As

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783397#comment-15783397 ] Bibin A Chundatt commented on YARN-6031: As [~sunilg] mentioned earlier ignoring application could

[jira] [Commented] (YARN-5969) FairShareComparator: Cache value of getResourceUsage for better performance

[ https://issues.apache.org/jira/browse/YARN-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783392#comment-15783392 ] Yufei Gu commented on YARN-5969: Absolutely! [~zsl2007], thanks for working on this. Any contribution to

[jira] [Commented] (YARN-5257) Fix unreleased resources and null dereferences

[ https://issues.apache.org/jira/browse/YARN-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783376#comment-15783376 ] Yufei Gu commented on YARN-5257: Thanks [~rkanter] for the review and commit. > Fix unreleased resources

[jira] [Commented] (YARN-5798) Handle FSPreemptionThread crashing due to a RuntimeException

[ https://issues.apache.org/jira/browse/YARN-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783375#comment-15783375 ] Karthik Kambatla commented on YARN-5798: Oh, and in RMFatalEventType, instead of calling it OTHERS,

[jira] [Commented] (YARN-5906) Update AppSchedulingInfo to use SchedulingPlacementSet

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

[jira] [Commented] (YARN-5798) Handle FSPreemptionThread crashing due to a RuntimeException

[ https://issues.apache.org/jira/browse/YARN-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783370#comment-15783370 ] Karthik Kambatla commented on YARN-5798: Thanks for picking this up, Yufei. Comments on the

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783232#comment-15783232 ] Daniel Templeton commented on YARN-6031: I agree that {{-force-recovery}} could cause a significant

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783133#comment-15783133 ] Daniel Templeton commented on YARN-5931: I agree, but it should be "collection", not "collections".

[jira] [Commented] (YARN-5906) Update AppSchedulingInfo to use SchedulingPlacementSet

[ https://issues.apache.org/jira/browse/YARN-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783106#comment-15783106 ] Sunil G commented on YARN-5906: --- Test case failures are unrelated. Will commit in a short while. > Update

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783083#comment-15783083 ] Rohith Sharma K S commented on YARN-5931: - I think this sentence is more meaning full. "When you

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783073#comment-15783073 ] Sunil G commented on YARN-6031: --- Yes. Makes sense. This is more less a work for admin then. I am not so sure

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783025#comment-15783025 ] Daniel Templeton commented on YARN-6031: bq. max_applications may hit and valid apps may get

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15783002#comment-15783002 ] Daniel Templeton commented on YARN-5931: Thanks for the update. Two more things: * This one is

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782995#comment-15782995 ] Sunil G commented on YARN-6031: --- Yes [~templedf]. You are correct. We will end up having many flaky apps in

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782984#comment-15782984 ] Daniel Templeton commented on YARN-6031: Yep, tests are needed. Love the long explanatory comment.

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782814#comment-15782814 ] Sunil G edited comment on YARN-6031 at 12/28/16 1:04 PM: - Thanks [~Ying Zhang],

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782814#comment-15782814 ] Sunil G commented on YARN-6031: --- Thanks [~Ying Zhang], Overall approach makes sense to me. You are basically

[jira] [Commented] (YARN-6024) Capacity Scheduler 'continuous reservation looking' doesn't work when sum of queue's used and reserved resources is equal to max

[ https://issues.apache.org/jira/browse/YARN-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782613#comment-15782613 ] Sunil G commented on YARN-6024: --- Committed {{YARN-6024.001.patch}} to trunk/branch-2/branch-2.8 and

[jira] [Commented] (YARN-5719) Enforce a C standard for native container-executor

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

[jira] [Comment Edited] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782566#comment-15782566 ] Ying Zhang edited comment on YARN-6031 at 12/28/16 10:22 AM: - Uploaded a patch,

[jira] [Commented] (YARN-6029) CapacityScheduler deadlock when ParentQueue#getQueueUserAclInfo is called by Thread_A at the moment that Thread_B calls LeafQueue#assignContainers to release a reserved

[ https://issues.apache.org/jira/browse/YARN-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782578#comment-15782578 ] Tao Yang commented on YARN-6029: Thanks [~wangda] & [~Naganarasimha] ! {quote} Agree but IIUC based on 2.8

[jira] [Updated] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ying Zhang updated YARN-6031: - Attachment: YARN-6031.001.patch > Application recovery failed after disabling node label >

[jira] [Commented] (YARN-6031) Application recovery failed after disabling node label

[ https://issues.apache.org/jira/browse/YARN-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782566#comment-15782566 ] Ying Zhang commented on YARN-6031: -- Uploaded a patch, which is based on [~leftnoteasy]'s comment on

[jira] [Created] (YARN-6034) Add support better logging in container-executor

Varun Vasudev created YARN-6034: --- Summary: Add support better logging in container-executor Key: YARN-6034 URL: https://issues.apache.org/jira/browse/YARN-6034 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-6033) Add support for sections in container-executor configuration file

Varun Vasudev created YARN-6033: --- Summary: Add support for sections in container-executor configuration file Key: YARN-6033 URL: https://issues.apache.org/jira/browse/YARN-6033 Project: Hadoop YARN

[jira] [Updated] (YARN-5719) Enforce a C standard for native container-executor

[ https://issues.apache.org/jira/browse/YARN-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-5719: Assignee: Chris Douglas > Enforce a C standard for native container-executor >

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

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

[jira] [Commented] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15782376#comment-15782376 ] Sunil G commented on YARN-5931: --- Thanks [~rohithsharma] Looks fine. I will wait for [~templedf] also. >

[jira] [Updated] (YARN-5931) Document timeout interfaces CLI and REST APIs

[ https://issues.apache.org/jira/browse/YARN-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-5931: Attachment: YARN-5931.3.patch Updated patch fixing review comments > Document timeout