[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

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

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073347#comment-15073347 ] sandflee commented on YARN-4495: Hi [~jianhe] [~wangda] [~mding] , do you think the change is necessary ?

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073355#comment-15073355 ] MENG DING commented on YARN-4495: - Hi, [~sandflee] I was just thinking would it be simpler to modify the

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073360#comment-15073360 ] Jun Gong commented on YARN-3480: [~jianhe] Thanks for suggestion. Attach a new patch to fix it. > Recovery

[jira] [Updated] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3480: --- Attachment: YARN-3480.14.patch > Recovery may get very slow with lots of services with lots of app-attempts >

[jira] [Commented] (YARN-4522) Queue acl can be checked at app submission

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

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073375#comment-15073375 ] Wangda Tan commented on YARN-4495: -- +1 to what [~mding] suggested, AMRMClientAsync should handle

[jira] [Commented] (YARN-4522) Queue acl can be checked at app submission

[ https://issues.apache.org/jira/browse/YARN-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073379#comment-15073379 ] Wangda Tan commented on YARN-4522: -- Patch generally looks good, thanks [~jianhe]. With this patch,

[jira] [Updated] (YARN-4098) Document ApplicationPriority feature

[ https://issues.apache.org/jira/browse/YARN-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4098: Attachment: (was: 0004-YARN-4098.patch) > Document ApplicationPriority feature >

[jira] [Commented] (YARN-4098) Document ApplicationPriority feature

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

[jira] [Commented] (YARN-4520) FinishAppEvent is leaked in leveldb if no app's container running on this node

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

[jira] [Updated] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4495: --- Attachment: YARN-4495.01.patch just protocol change, add FailedResourceChange to AllocateResponse, represents

[jira] [Updated] (YARN-4098) Document ApplicationPriority feature

[ https://issues.apache.org/jira/browse/YARN-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4098: Attachment: 0004-YARN-4098.patch > Document ApplicationPriority feature >

[jira] [Updated] (YARN-4098) Document ApplicationPriority feature

[ https://issues.apache.org/jira/browse/YARN-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4098: Attachment: 0004-YARN-4098.patch > Document ApplicationPriority feature >

[jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072555#comment-15072555 ] Rohith Sharma K S commented on YARN-3692: - Going through for the implementation, this JIRA required

[jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072573#comment-15072573 ] Naganarasimha G R commented on YARN-3692: - Thanks for sharing you thoughts [~rohithsharma], +1 for

[jira] [Created] (YARN-4521) Test Failure: TestJobHistoryEventHandler.testTimelineEventHandling

Mohammad Shahid Khan created YARN-4521: -- Summary: Test Failure: TestJobHistoryEventHandler.testTimelineEventHandling Key: YARN-4521 URL: https://issues.apache.org/jira/browse/YARN-4521 Project:

[jira] [Commented] (YARN-4505) TestJobHistoryEventHandler.testTimelineEventHandling fails on trunk because of NPE

[ https://issues.apache.org/jira/browse/YARN-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072794#comment-15072794 ] Varun Saxena commented on YARN-4505: Yeah, thats correct...Pls move it. >

[jira] [Updated] (YARN-4505) TestJobHistoryEventHandler.testTimelineEventHandling fails on trunk because of NPE

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

[jira] [Updated] (YARN-1382) NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged

[ https://issues.apache.org/jira/browse/YARN-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-1382: Attachment: 0001-YARN-1382.patch Updating the patch, kindly review > NodeListManager has a

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

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

[jira] [Commented] (YARN-4521) Test Failure: TestJobHistoryEventHandler.testTimelineEventHandling

[ https://issues.apache.org/jira/browse/YARN-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072675#comment-15072675 ] Varun Saxena commented on YARN-4521: Duplicate of YARN-4505 > Test Failure:

[jira] [Commented] (YARN-1382) NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged

[ https://issues.apache.org/jira/browse/YARN-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072688#comment-15072688 ] Rohith Sharma K S commented on YARN-1382: - {{NodesListManager#getUnusableNodes}} never used, so

[jira] [Commented] (YARN-1382) NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged

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

[jira] [Updated] (YARN-1382) NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged

[ https://issues.apache.org/jira/browse/YARN-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-1382: Target Version/s: 2.8.0 > NodeListManager has a memory leak, unusableRMNodesConcurrentSet is

[jira] [Commented] (YARN-4505) TestJobHistoryEventHandler.testTimelineEventHandling fails on trunk because of NPE

[ https://issues.apache.org/jira/browse/YARN-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072785#comment-15072785 ] Naganarasimha G R commented on YARN-4505: - [~varun_saxena], i think we need to move this to Map

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072873#comment-15072873 ] MENG DING commented on YARN-4519: - I feel that the correct solution would be simply put all decrease

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072880#comment-15072880 ] MENG DING commented on YARN-4138: - Hi, [~sandflee] I think this issue depends on YARN-4519. Will suspend

[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073189#comment-15073189 ] Rich Haase commented on YARN-4257: -- The failing tests don't appear to be related to this patch. Not sure

[jira] [Created] (YARN-4522) Queue acl can be checked at app submission

Jian He created YARN-4522: - Summary: Queue acl can be checked at app submission Key: YARN-4522 URL: https://issues.apache.org/jira/browse/YARN-4522 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4482) Default values of several config parameters are missing

[ https://issues.apache.org/jira/browse/YARN-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073024#comment-15073024 ] Tianyin Xu commented on YARN-4482: -- Thanks, [~mohdshahidkhan]! But why it's won't fix @_@ It's terribly

[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073044#comment-15073044 ] Wangda Tan commented on YARN-4257: -- Hi [~rhaase], I didn't see patch attached to this JIRA, could you

[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073053#comment-15073053 ] Rich Haase commented on YARN-4257: -- Just uploaded the fixed patch. I found a couple import changes that

[jira] [Updated] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Haase updated YARN-4257: - Attachment: YARN-4257.patch > Move scheduler validateConf method to AbstractYarnScheduler and make it >

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073067#comment-15073067 ] MENG DING commented on YARN-4519: - This approach would be simpler, at the expense of acquiring a CS lock in

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072993#comment-15072993 ] Wangda Tan commented on YARN-4519: -- Thanks [~jianhe] found this issue and analysis from

[jira] [Comment Edited] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072993#comment-15072993 ] Wangda Tan edited comment on YARN-4519 at 12/28/15 6:43 PM: Thanks [~jianhe]

[jira] [Updated] (YARN-4516) [YARN-3368] Use em-table to better render tables

[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4516: - Assignee: Li Lu > [YARN-3368] Use em-table to better render tables >

[jira] [Updated] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Haase updated YARN-4257: - Attachment: (was: YARN-4257.patch) > Move scheduler validateConf method to AbstractYarnScheduler and

[jira] [Commented] (YARN-4257) Move scheduler validateConf method to AbstractYarnScheduler and make it protected

[ https://issues.apache.org/jira/browse/YARN-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073003#comment-15073003 ] Rich Haase commented on YARN-4257: -- Hi [~wangda], I'm uploading a patch that tests out in my local build

[jira] [Commented] (YARN-4098) Document ApplicationPriority feature

[ https://issues.apache.org/jira/browse/YARN-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073029#comment-15073029 ] Jian He commented on YARN-4098: --- sorry, pasted wrong, earlier it was saying "submitted with different

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073076#comment-15073076 ] Wangda Tan commented on YARN-4519: -- bq. I also think that it is necessary to move the logic of creating

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073400#comment-15073400 ] sandflee commented on YARN-4495: Thanks [~mding], [~wangda], yes this could simple the code and cover the

[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables

[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073493#comment-15073493 ] Sreenath Somarajapuram commented on YARN-4516: -- Thanks [~gtCarrera9] That sounds like a good

[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=15073428#comment-15073428 ] Naganarasimha G R commented on YARN-3215: - Hi [~wangda], Few concerns on the approach which you

[jira] [Updated] (YARN-4522) Queue acl can be checked at app submission

[ https://issues.apache.org/jira/browse/YARN-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4522: -- Attachment: YARN-4522.2.patch > Queue acl can be checked at app submission >

[jira] [Commented] (YARN-4522) Queue acl can be checked at app submission

[ https://issues.apache.org/jira/browse/YARN-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073436#comment-15073436 ] Jian He commented on YARN-4522: --- upload a new patch that fixed the failure > Queue acl can be checked at app

[jira] [Updated] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3480: --- Attachment: YARN-3480.15.patch Fix whitespace error. > Recovery may get very slow with lots of services with

[jira] [Updated] (YARN-4505) TestJobHistoryEventHandler.testTimelineEventHandling fails on trunk because of NPE

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

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

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

[jira] [Commented] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

[ https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073472#comment-15073472 ] sandflee commented on YARN-4495: [~mding] [~wangda] one problem, seems hadoop rpc could only transfer

[jira] [Commented] (YARN-4522) Queue acl can be checked at app submission

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

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073258#comment-15073258 ] Jian He commented on YARN-3480: --- actually, one more comment: below code introduces one more loop for all

[jira] [Updated] (YARN-4522) Queue acl can be checked at app submission

[ https://issues.apache.org/jira/browse/YARN-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4522: -- Attachment: YARN-4522.1.patch > Queue acl can be checked at app submission >

[jira] [Commented] (YARN-4417) Make RM and Timeline-server REST APIs more consistent

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

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073319#comment-15073319 ] Wangda Tan commented on YARN-4519: -- [~mding], I haven't started, please go ahead if you're interested. We

[jira] [Commented] (YARN-4438) Implement RM leader election with curator

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

[jira] [Updated] (YARN-4438) Implement RM leader election with curator

[ https://issues.apache.org/jira/browse/YARN-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4438: -- Attachment: YARN-4438.4.patch upload a new patch that fixed the comments > Implement RM leader election with

[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables

[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073305#comment-15073305 ] Li Lu commented on YARN-4516: - Thanks [~leftnoteasy] and [~Sreenath]! Now I've set up em-table for ats v2 web

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073316#comment-15073316 ] MENG DING commented on YARN-4519: - Yes the race only happens when computing delta resource, and yes it also

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073321#comment-15073321 ] MENG DING commented on YARN-4519: - Agreed :-) > potential deadlock of CapacityScheduler between decrease

[jira] [Assigned] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING reassigned YARN-4519: --- Assignee: MENG DING > potential deadlock of CapacityScheduler between decrease container and assign

[jira] [Commented] (YARN-3328) There's no way to rebuild containers Managed by NMClientAsync If AM restart

[ https://issues.apache.org/jira/browse/YARN-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073587#comment-15073587 ] sandflee commented on YARN-3328: we fix this problem by removing container state machine in

[jira] [Commented] (YARN-3480) Recovery may get very slow with lots of services with lots of app-attempts

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