[jira] [Commented] (YARN-3382) Some of UserMetricsInfo metrics are incorrectly set to root queue metrics

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

[jira] [Commented] (YARN-3127) Apphistory url crashes when RM switches with ATS enabled

[ https://issues.apache.org/jira/browse/YARN-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492963#comment-14492963 ] Xuan Gong commented on YARN-3127: - [~Naganarasimha] Sorry for the late reply. So, the

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492798#comment-14492798 ] Wangda Tan commented on YARN-3361: -- Failed tests can get passed locally, and aren't

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492823#comment-14492823 ] Zhijie Shen commented on YARN-3046: --- Junping, thanks for the patch. Overall it looks good

[jira] [Updated] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3347: Attachment: YARN-3347.4.patch Improve YARN log command to get AMContainer logs as well as running

[jira] [Updated] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3443: Attachment: YARN-3443.005.patch hi [~djp] , uploading a new patch. Please take a look.

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492937#comment-14492937 ] Hadoop QA commented on YARN-3443: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492879#comment-14492879 ] Hadoop QA commented on YARN-3472: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492956#comment-14492956 ] Hadoop QA commented on YARN-3347: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3382) Some of UserMetricsInfo metrics are incorrectly set to root queue metrics

[ https://issues.apache.org/jira/browse/YARN-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492712#comment-14492712 ] Jian He commented on YARN-3382: --- lgtm, +1 Some of UserMetricsInfo metrics are incorrectly

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492883#comment-14492883 ] Xuan Gong commented on YARN-3347: - new patch addressed all the latest comments Improve

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492978#comment-14492978 ] Sidharta Seethana commented on YARN-3443: - The javadoc warnings are unrelated to

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492951#comment-14492951 ] Nathan Roberts commented on YARN-3361: -- Hi [~leftnoteasy]. One comment/question.

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

[ https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492748#comment-14492748 ] Wei Yan commented on YARN-2618: --- [~kasha], help commit the patch? Avoid over-allocation of

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492791#comment-14492791 ] Hadoop QA commented on YARN-3361: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492792#comment-14492792 ] Ashwin Shankar commented on YARN-3453: -- [~peng.zhang], bq. Calculator should be

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493026#comment-14493026 ] Wangda Tan commented on YARN-3361: -- Hi [~nroberts], Good point, we should use partition

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493156#comment-14493156 ] Zhijie Shen commented on YARN-3134: --- Li, thanks for uploading the POC patch. I put some

[jira] [Commented] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493172#comment-14493172 ] Inigo Goiri commented on YARN-3481: --- To make YARN aware of the actual use of resources in

[jira] [Created] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

Inigo Goiri created YARN-3481: - Summary: Report NM aggregated container resource utilization in heartbeat Key: YARN-3481 URL: https://issues.apache.org/jira/browse/YARN-3481 Project: Hadoop YARN

[jira] [Commented] (YARN-3394) WebApplication proxy documentation is incomplete

[ https://issues.apache.org/jira/browse/YARN-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493010#comment-14493010 ] Jian He commented on YARN-3394: --- +1 , committing shortly WebApplication proxy

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493020#comment-14493020 ] Nathan Roberts commented on YARN-3388: -- Thanks [~leftnoteasy] for the comments.

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493093#comment-14493093 ] Xuan Gong commented on YARN-3347: - -1 eclipse:eclipse is not related. Can compile mvn

[jira] [Commented] (YARN-3389) Avoid race conditions when attempts operate on shared states concurrently

[ https://issues.apache.org/jira/browse/YARN-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493112#comment-14493112 ] Jian He commented on YARN-3389: --- [~hex108], did you see this happen in reality ? Given that

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493177#comment-14493177 ] Inigo Goiri commented on YARN-3482: --- The NM would have an interface (maybe a

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493041#comment-14493041 ] Wangda Tan commented on YARN-3388: -- [~nroberts], Make sense to me. I really appreciate if

[jira] [Commented] (YARN-3266) RMContext inactiveNodes should have NodeId as map key

[ https://issues.apache.org/jira/browse/YARN-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493063#comment-14493063 ] Jian He commented on YARN-3266: --- I found given that RMContext#getRMNodes uses NodeId, do you

[jira] [Commented] (YARN-3266) RMContext inactiveNodes should have NodeId as map key

[ https://issues.apache.org/jira/browse/YARN-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493033#comment-14493033 ] Jian He commented on YARN-3266: --- lgtm, +1 RMContext inactiveNodes should have NodeId as

[jira] [Commented] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493085#comment-14493085 ] Bartosz Ługowski commented on YARN-1621: Failed tests are not related with this

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493080#comment-14493080 ] Jian He commented on YARN-3472: --- +1 Possible leak in DelegationTokenRenewer#allTokens

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

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

[jira] [Created] (YARN-3482) Report NM available resources in heartbeat

Inigo Goiri created YARN-3482: - Summary: Report NM available resources in heartbeat Key: YARN-3482 URL: https://issues.apache.org/jira/browse/YARN-3482 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-3319) Implement a FairOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3319: -- Attachment: YARN-3319.58.patch Implement a FairOrderingPolicy --

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493215#comment-14493215 ] Zhijie Shen commented on YARN-3134: --- Another issue: It seems we don't need to build

[jira] [Updated] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3318: -- Attachment: YARN-3318.58.patch Missed attaching ResourceUsage Create Initial OrderingPolicy Framework

[jira] [Commented] (YARN-3483) Easier access to resource metrics

[ https://issues.apache.org/jira/browse/YARN-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493239#comment-14493239 ] Inigo Goiri commented on YARN-3483: --- The use case for this is being able to access

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493374#comment-14493374 ] Hadoop QA commented on YARN-3318: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3394) WebApplication proxy documentation is incomplete

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

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

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

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493479#comment-14493479 ] Hadoop QA commented on YARN-3318: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493310#comment-14493310 ] Junping Du commented on YARN-3347: -- Latest patch LGTM. Verified locally that mvn

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493401#comment-14493401 ] Junping Du commented on YARN-3443: -- +1. Latest patch LGTM. Double check all javadoc

[jira] [Commented] (YARN-3266) RMContext inactiveNodes should have NodeId as map key

[ https://issues.apache.org/jira/browse/YARN-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493414#comment-14493414 ] Chengbing Liu commented on YARN-3266: - {quote} I found given that RMContext#getRMNodes

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

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

[jira] [Updated] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3318: -- Attachment: YARN-3318.57.patch Better ResourceUsage usage Create Initial OrderingPolicy Framework and

[jira] [Updated] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3463: -- Attachment: YARN-3643.58.patch Integrate OrderingPolicy Framework with CapacityScheduler

[jira] [Updated] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3318: -- Attachment: YARN-3318.59.patch checkpatch fixes Create Initial OrderingPolicy Framework and

[jira] [Commented] (YARN-3394) WebApplication proxy documentation is incomplete

[ https://issues.apache.org/jira/browse/YARN-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493352#comment-14493352 ] Naganarasimha G R commented on YARN-3394: - Thanks [~jianhe] for reviewing and

[jira] [Updated] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3366: Attachment: YARN-3366.004.patch Uploading rebased patch Outbound network bandwidth :

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493235#comment-14493235 ] Li Lu commented on YARN-3134: - Hi [~vrushalic] and [~zjshen]! Thanks for the comments! About

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493237#comment-14493237 ] Hadoop QA commented on YARN-3318: - {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (YARN-3483) Easier access to resource metrics

Inigo Goiri created YARN-3483: - Summary: Easier access to resource metrics Key: YARN-3483 URL: https://issues.apache.org/jira/browse/YARN-3483 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-3366: Attachment: YARN-3366.005.patch Uploaded a new patch with findbugs warnings fixed.

[jira] [Updated] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

[ https://issues.apache.org/jira/browse/YARN-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3451: - Attachment: 0001-YARN-3451.patch Rebased the same patch for triggering jenkins Add start time and Elapsed in

[jira] [Commented] (YARN-3266) RMContext inactiveNodes should have NodeId as map key

[ https://issues.apache.org/jira/browse/YARN-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493506#comment-14493506 ] Jian He commented on YARN-3266: --- since it's internal to RM only, I think it's ok. your

[jira] [Updated] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

[ https://issues.apache.org/jira/browse/YARN-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3451: - Summary: Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

[jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493516#comment-14493516 ] Hadoop QA commented on YARN-3366: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3404) View the queue name to YARN Application page

[ https://issues.apache.org/jira/browse/YARN-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryu Kobayashi updated YARN-3404: Attachment: YARN-3404.3.patch Now that it have conflict, I created a new patch. View the queue

[jira] [Commented] (YARN-3404) View the queue name to YARN Application page

[ https://issues.apache.org/jira/browse/YARN-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493588#comment-14493588 ] Hadoop QA commented on YARN-3404: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493529#comment-14493529 ] Peng Zhang commented on YARN-3453: -- [~ashwinshankar77] bq. Would it help if we have a

[jira] [Commented] (YARN-3462) Patches applied for YARN-2424 are inconsistent between trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492676#comment-14492676 ] Naganarasimha G R commented on YARN-3462: - Hi [~qwertymaniac], hope you can take a

[jira] [Commented] (YARN-3475) Invalid Resource Exception could be handled properly when cores not available

[ https://issues.apache.org/jira/browse/YARN-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492112#comment-14492112 ] Naganarasimha G R commented on YARN-3475: - hi [~bibinchundatt] Looks more like a

[jira] [Updated] (YARN-3475) Invalid Resource Exception could be handled properly when cores not available

[ https://issues.apache.org/jira/browse/YARN-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3475: --- Summary: Invalid Resource Exception could be handled properly when cores not available (was:

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492007#comment-14492007 ] Hadoop QA commented on YARN-3318: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3478) FairScheduler page not performed because different enum of YarnApplicationState and RMAppState

[ https://issues.apache.org/jira/browse/YARN-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491955#comment-14491955 ] Xu Chen commented on YARN-3478: --- Thanks Naganarasimha G R , fix it, uploaded again.

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491959#comment-14491959 ] Craig Welch commented on YARN-3318: --- added comments to compoundcomparator, re-introduced

[jira] [Updated] (YARN-3478) FairScheduler page not performed because different enum of YarnApplicationState and RMAppState

[ https://issues.apache.org/jira/browse/YARN-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xu Chen updated YARN-3478: -- Attachment: YARN-3478.2.patch FairScheduler page not performed because different enum of YarnApplicationState

[jira] [Updated] (YARN-3478) FairScheduler page not performed because different enum of YarnApplicationState and RMAppState

[ https://issues.apache.org/jira/browse/YARN-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xu Chen updated YARN-3478: -- Attachment: YARN-3478.3.patch FairScheduler page not performed because different enum of YarnApplicationState

[jira] [Created] (YARN-3479) RM switch sanity check for Resource not happening

Bibin A Chundatt created YARN-3479: -- Summary: RM switch sanity check for Resource not happening Key: YARN-3479 URL: https://issues.apache.org/jira/browse/YARN-3479 Project: Hadoop YARN

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492228#comment-14492228 ] Rohith commented on YARN-3472: -- bq. But I am surprised why the test were not failing earlier?

[jira] [Updated] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3472: - Attachment: 0002-YARN-3472.patch Updated the patch adding test Possible leak in DelegationTokenRenewer#allTokens

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492128#comment-14492128 ] Rohith commented on YARN-3472: -- IIUC the test method

[jira] [Commented] (YARN-3472) Possible leak in DelegationTokenRenewer#allTokens

[ https://issues.apache.org/jira/browse/YARN-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492332#comment-14492332 ] Hadoop QA commented on YARN-3472: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3453) Fair Scheduler : Parts of preemption logic uses DefaultResourceCalculator even in DRF mode causing thrashing

[ https://issues.apache.org/jira/browse/YARN-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492440#comment-14492440 ] Peng Zhang commented on YARN-3453: -- [~ashwinshankar77] I‘ve the same problem in our

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492467#comment-14492467 ] Peng Zhang commented on YARN-3405: -- Other issues for preemption during development, need

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492340#comment-14492340 ] Junping Du commented on YARN-3347: -- Thanks [~xgong] for updating the patch! The patch

[jira] [Commented] (YARN-3414) FairScheduler's preemption may cause livelock

[ https://issues.apache.org/jira/browse/YARN-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492405#comment-14492405 ] Peng Zhang commented on YARN-3414: -- It has the same root cause like YARN-3405.

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492402#comment-14492402 ] Peng Zhang commented on YARN-3405: -- I uploaded one patch for this. This patch updated

[jira] [Created] (YARN-3480) Make AM max attempts stored in RMStateStore to be configurable

Jun Gong created YARN-3480: -- Summary: Make AM max attempts stored in RMStateStore to be configurable Key: YARN-3480 URL: https://issues.apache.org/jira/browse/YARN-3480 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3389) Avoid race conditions when attempts operate on shared states concurrently

[ https://issues.apache.org/jira/browse/YARN-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492374#comment-14492374 ] Jun Gong commented on YARN-3389: [~jianhe] Kindly review it please. Thank you. Avoid race

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Attachment: YARN-3405.01.patch FairScheduler's preemption cannot happen between sibling in some case

[jira] [Updated] (YARN-3476) Nodemanager can fail to delete local logs if log aggregation fails

[ https://issues.apache.org/jira/browse/YARN-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3476: - Attachment: 0001-YARN-3476.patch Nodemanager can fail to delete local logs if log aggregation fails

[jira] [Commented] (YARN-3318) Create Initial OrderingPolicy Framework and FifoOrderingPolicy

[ https://issues.apache.org/jira/browse/YARN-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492615#comment-14492615 ] Craig Welch commented on YARN-3318: --- Looking again at using ResourceUsage instead of the

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492643#comment-14492643 ] Vinod Kumar Vavilapalli commented on YARN-3443: --- bq. I would prefer we

[jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: - Attachment: YARN-3361.10.patch Hi [~vinodkv], Thanks for your comments, bq. You should have added a

[jira] [Commented] (YARN-3286) Cleanup RMNode#ReconnectNodeTransition

[ https://issues.apache.org/jira/browse/YARN-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492664#comment-14492664 ] Rohith commented on YARN-3286: -- Yes, If the node is Reconnecting, scheduler#removeNode kill

[jira] [Commented] (YARN-3443) Create a 'ResourceHandler' subsystem to ease addition of support for new resource types on the NM

[ https://issues.apache.org/jira/browse/YARN-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492669#comment-14492669 ] Junping Du commented on YARN-3443: -- Thanks [~vinodkv] for comments and confirmation on

[jira] [Commented] (YARN-3476) Nodemanager can fail to delete local logs if log aggregation fails

[ https://issues.apache.org/jira/browse/YARN-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492593#comment-14492593 ] Rohith commented on YARN-3476: -- bq. Not all of the application's logs were available in HDFS

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492482#comment-14492482 ] Hadoop QA commented on YARN-3405: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492514#comment-14492514 ] Vinod Kumar Vavilapalli commented on YARN-3361: --- Quickly scanned through.