[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=15074052#comment-15074052 ] sandflee commented on YARN-4495: better to pass why resource change request is failed. > add a way to tell

[jira] [Commented] (YARN-4232) TopCLI console shows exceptions for help command

[ https://issues.apache.org/jira/browse/YARN-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074119#comment-15074119 ] Junping Du commented on YARN-4232: -- Shall we instead support HA in top CLI? CC [~vvasudev]. > TopCLI

[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=15074082#comment-15074082 ] MENG DING commented on YARN-4495: - I guess my point is if you are not going to do any automated action upon

[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=15073991#comment-15073991 ] MENG DING commented on YARN-4519: - Hi, [~sandflee] The delta resource is the difference between currently

[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=15074028#comment-15074028 ] MENG DING commented on YARN-4495: - Hi, [~sandflee] What is your specific use case? Do you plan to catch

[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=15074049#comment-15074049 ] sandflee commented on YARN-4495: the main problem is we couldn't pass containerId to

[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=15074038#comment-15074038 ] sandflee commented on YARN-4519: got it, thanks [~mding]! > potential deadlock of CapacityScheduler

[jira] [Commented] (YARN-4232) TopCLI console shows exceptions for help command

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

[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=15074393#comment-15074393 ] Karthik Kambatla commented on YARN-4257: [~leftnoteasy] - really appreciate the ping, haven't seen

[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=15074439#comment-15074439 ] Wangda Tan commented on YARN-4522: -- Looks good, +1. > Queue acl can be checked at app submission >

[jira] [Commented] (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:comment-tabpanel=15074561#comment-15074561 ] Li Lu commented on YARN-4265: - Sorry by saying YARN-4234 I'm actually meaning YARN-3942. > Provide new

[jira] [Commented] (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:comment-tabpanel=15074560#comment-15074560 ] Li Lu commented on YARN-4265: - BTW, I've got some offline discussion with [~jlowe]. In general, we agreed to

[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=15074424#comment-15074424 ] Wangda Tan commented on YARN-4257: -- Corrected JIRA id in my last comment: YARN-1408 -> YARN-1488 > Move

[jira] [Comment Edited] (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=15074422#comment-15074422 ] Wangda Tan edited comment on YARN-4257 at 12/29/15 11:24 PM: - Thanks

[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=15074459#comment-15074459 ] Hudson commented on YARN-3480: -- FAILURE: Integrated in Hadoop-trunk-Commit #9036 (See

[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=15074515#comment-15074515 ] Jun Gong commented on YARN-3480: Thanks [~jianhe] for the suggestion, review and commit! > Recovery may

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

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

[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=15074530#comment-15074530 ] Li Lu commented on YARN-4516: - OK I've updated my local em-table. [~Sreenath] one more (probably silly)

[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=15074435#comment-15074435 ] Rich Haase commented on YARN-4257: -- [~leftnoteasy] Agreed. Doesn't make sense to change validateConf if

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074433#comment-15074433 ] Hadoop QA commented on YARN-4524: - | (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.5.patch > Implement RM leader election with curator >

[jira] [Updated] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

[ https://issues.apache.org/jira/browse/YARN-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4526: --- Attachment: yarn-4526-1.patch Uploading a patch that makes SystemClock a singleton. In

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

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

[jira] [Created] (YARN-4525) Bug in RLESparseResourceAllocation.getRangeOverlapping(...)

Ishai Menache created YARN-4525: --- Summary: Bug in RLESparseResourceAllocation.getRangeOverlapping(...) Key: YARN-4525 URL: https://issues.apache.org/jira/browse/YARN-4525 Project: Hadoop YARN

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074375#comment-15074375 ] Wangda Tan commented on YARN-4524: -- Thanks [~kasha] working on this, this is very useful for our future

[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=15074399#comment-15074399 ] Karthik Kambatla commented on YARN-4257: Just read the remainder of the description regarding

[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=15074422#comment-15074422 ] Wangda Tan commented on YARN-4257: -- Thanks [~kasha]/[~rhaase], 0 resource makes sense to me if container

[jira] [Updated] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4524: --- Attachment: yarn-4524-2.patch Thanks Wangda. Good catch on the move() call, removing those

[jira] [Commented] (YARN-4470) Application Master in-place upgrade

[ https://issues.apache.org/jira/browse/YARN-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074431#comment-15074431 ] Jian He commented on YARN-4470: --- My concern on this is that a lot of complexity is added into app/attempt

[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=15074404#comment-15074404 ] Rich Haase commented on YARN-4257: -- [~kasha] I can update the patch to revert the changes to the

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074472#comment-15074472 ] Jian He commented on YARN-4479: --- - For finished attempt, I think we do not need to re-add into scheduler, so

[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=15074473#comment-15074473 ] sandflee commented on YARN-4495: to [~mding], 1, we have a StateMachine in AM to track every

[jira] [Created] (YARN-4526) Make SystemClock singleton so AppSchedulingInfo could use it

Karthik Kambatla created YARN-4526: -- Summary: Make SystemClock singleton so AppSchedulingInfo could use it Key: YARN-4526 URL: https://issues.apache.org/jira/browse/YARN-4526 Project: Hadoop YARN

[jira] [Updated] (YARN-4523) Extend ReservationAllocation to support node labels

[ https://issues.apache.org/jira/browse/YARN-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4523: - Description: ReservationAllocation is data structure that tracks the resources allocated to 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=15074308#comment-15074308 ] Wangda Tan commented on YARN-4495: -- Hi [~sandflee], bq. .. one problem, seems hadoop rpc could only

[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=15074334#comment-15074334 ] Wangda Tan commented on YARN-4257: -- Thanks [~rhaase], Patch looks good to me. [~kasha], since the patch

[jira] [Commented] (YARN-4525) Bug in RLESparseResourceAllocation.getRangeOverlapping(...)

[ https://issues.apache.org/jira/browse/YARN-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074355#comment-15074355 ] Ishai Menache commented on YARN-4525: - We suggest the following fix: current code: a = a.headMap(end,

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074291#comment-15074291 ] Karthik Kambatla commented on YARN-4524: [~leftnoteasy] - with your recent node-label work, you

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074236#comment-15074236 ] Karthik Kambatla commented on YARN-4524: I am taking a stab at it, and it appears some of the

[jira] [Updated] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4524: --- Attachment: yarn-4524-1.patch A somewhat simpler version of AppSchedulingInfo - all methods

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074267#comment-15074267 ] Wangda Tan commented on YARN-4224: -- Hi [~varun_saxena], I would prefer to response UID to REST client

[jira] [Commented] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074307#comment-15074307 ] Subru Krishnan commented on YARN-2575: -- Thanks @Sean Po for the updated patch. It looks mostly good to

[jira] [Commented] (YARN-4315) NaN in Queue percentage for cluster apps page

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

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

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074351#comment-15074351 ] Wangda Tan commented on YARN-4304: -- 1) LeafQueue: - amLimitForEmptyLabel -> amLimit? - Since

[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=15074360#comment-15074360 ] Li Lu commented on YARN-4516: - Thanks [~Sreenath]! Shall I redo npm install to get this feature? >

[jira] [Commented] (YARN-4195) Support of node-labels in the ReservationSystem "Plan"

[ https://issues.apache.org/jira/browse/YARN-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074229#comment-15074229 ] Subru Krishnan commented on YARN-4195: -- [~curino], thanks for driving this. I looked at the patch and

[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=15074330#comment-15074330 ] Wangda Tan commented on YARN-3215: -- Hi [~Naganarasimha], bq. Any concerns in doing this way The biggest

[jira] [Created] (YARN-4523) Extend ReservationAllocation to support node labels

Subru Krishnan created YARN-4523: Summary: Extend ReservationAllocation to support node labels Key: YARN-4523 URL: https://issues.apache.org/jira/browse/YARN-4523 Project: Hadoop YARN Issue

[jira] [Assigned] (YARN-4523) Extend ReservationAllocation to support node labels

[ https://issues.apache.org/jira/browse/YARN-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-4523: Assignee: Subru Krishnan (was: Alexey Tumanov) > Extend ReservationAllocation to support

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074613#comment-15074613 ] Karthik Kambatla commented on YARN-4524: I think the test failures are unrelated, I have seen them

[jira] [Commented] (YARN-4224) Change the ATSv2 reader side REST interface to conform to current REST APIs' in YARN

[ https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074661#comment-15074661 ] Varun Saxena commented on YARN-4224: Thanks [~leftnoteasy]. I suspected the same as cluster and flow

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

[jira] [Commented] (YARN-4479) Retrospect app-priority in pendingOrderingPolicy during recovering applications

[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074705#comment-15074705 ] Rohith Sharma K S commented on YARN-4479: - bq. For finished attempt, I think we do not need to

[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=15074604#comment-15074604 ] Rohith Sharma K S commented on YARN-1382: - [~djp] would you have look at the patch whenever you are

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074614#comment-15074614 ] Karthik Kambatla commented on YARN-4524: The checkstyle issues are marginal, and I would like to

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

[ https://issues.apache.org/jira/browse/YARN-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Shahid Khan resolved YARN-4521. Resolution: Duplicate Duplicate of

[jira] [Commented] (YARN-3870) Providing raw container request information for fine scheduling

[ https://issues.apache.org/jira/browse/YARN-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074755#comment-15074755 ] Xianyin Xin commented on YARN-3870: --- +1 for adding an unique id for a resource request, but i would

[jira] [Commented] (YARN-4232) TopCLI console shows exceptions for help command

[ https://issues.apache.org/jira/browse/YARN-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074635#comment-15074635 ] Bibin A Chundatt commented on YARN-4232: [~djp] Thanks for looking into this. Support for HA can be

[jira] [Commented] (YARN-3870) Providing raw container request information for fine scheduling

[ https://issues.apache.org/jira/browse/YARN-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074658#comment-15074658 ] Karthik Kambatla commented on YARN-3870: +1 to improving the way we are storing ResourceRequests in

[jira] [Updated] (YARN-3607) Allow users to choose between failing the daemons vs failing the apps/containers

[ https://issues.apache.org/jira/browse/YARN-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3607: --- Assignee: (was: Karthik Kambatla) > Allow users to choose between failing the daemons vs

[jira] [Updated] (YARN-3607) Allow users to choose between failing the daemons vs failing the apps/containers

[ https://issues.apache.org/jira/browse/YARN-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3607: --- Target Version/s: 3.0.0 (was: 2.8.0) > Allow users to choose between failing the daemons vs

[jira] [Commented] (YARN-4524) Cleanup AppSchedulingInfo

[ https://issues.apache.org/jira/browse/YARN-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074674#comment-15074674 ] Wangda Tan commented on YARN-4524: -- Looks good, will commit tomorrow, thanks! > Cleanup AppSchedulingInfo

[jira] [Updated] (YARN-3933) Race condition when calling AbstractYarnScheduler.completedContainer.

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiwei Guo updated YARN-3933: - Attachment: YARN-3933.002.patch Rebase on latest trunk (based on commit d0a22ba) > Race condition when

[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: 0003-YARN-1382.patch > NodeListManager has a memory leak,

[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=15074595#comment-15074595 ] Hadoop QA commented on YARN-4438: - | (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: Affects Version/s: 2.7.1 2.6.2 > NodeListManager has a memory leak,

[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: 0002-YARN-1382.patch Updated the patch fixing checkstyle warnings.. >

[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=15074610#comment-15074610 ] Naganarasimha G R commented on YARN-3215: - Thanks for sharing your thoughts [~wangda], bq. I would

[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=15074682#comment-15074682 ] Mohammad Ghanavati commented on YARN-1382: -- The patch looks good to me. > NodeListManager has a

[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=15074681#comment-15074681 ] Mohammad Ghanavati commented on YARN-1382: -- Thanks for the patch. seems that there are some

[jira] [Commented] (YARN-3870) Providing raw container request information for fine scheduling

[ https://issues.apache.org/jira/browse/YARN-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074685#comment-15074685 ] Wangda Tan commented on YARN-3870: -- Hi [~kasha]/[~asuresh], I think this JIRA and YARN-4485 are

[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=15074693#comment-15074693 ] Rohith Sharma K S commented on YARN-1382: - oho, I did not do format, will upload new patch >

[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=15073622#comment-15073622 ] sandflee commented on YARN-4519: sorry, I don't understand 1, why should we put compute delta resource

[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=15073630#comment-15073630 ] Sreenath Somarajapuram commented on YARN-4516: -- [~gtCarrera9] I have added

[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=15073825#comment-15073825 ] Bibin A Chundatt commented on YARN-4521: Adding the updated jira ids MAPREDUCE-6593 and

[jira] [Commented] (YARN-4315) NaN in Queue percentage for cluster apps page

[ https://issues.apache.org/jira/browse/YARN-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073845#comment-15073845 ] Bibin A Chundatt commented on YARN-4315: [~leftnoteasy]. Thanks for review. > NaN in Queue

[jira] [Commented] (YARN-4232) TopCLI console shows exceptions for help command

[ https://issues.apache.org/jira/browse/YARN-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073901#comment-15073901 ] Bibin A Chundatt commented on YARN-4232: Hi [~rohithsharma] Could you please review the same. >

[jira] [Commented] (YARN-3940) Application moveToQueue should check NodeLabel permission

[ https://issues.apache.org/jira/browse/YARN-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073930#comment-15073930 ] Bibin A Chundatt commented on YARN-3940: Hi [~leftnoteasy] Sorry for delayed response. But if