[jira] [Updated] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4392: Attachment: YARN-4392.2.patch > ApplicationCreatedEvent event time resets after RM restart/failover >

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034604#comment-15034604 ] Daniel Templeton commented on YARN-4406: Looking at the {{NodesListManager}}, it looks to me like

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034633#comment-15034633 ] Eric Payne commented on YARN-4108: -- Thanks very much [~leftnoteasy] for creating this POC. Just a quick

[jira] [Updated] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4406: --- Assignee: (was: Daniel Templeton) > RM Web UI continues to show decommissioned nodes even

[jira] [Assigned] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton reassigned YARN-4406: -- Assignee: Daniel Templeton > RM Web UI continues to show decommissioned nodes even

[jira] [Updated] (YARN-4405) Support node label store in non-appendable file system

[ https://issues.apache.org/jira/browse/YARN-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4405: - Attachment: YARN-4405.1.patch Attached initial patch for review. > Support node label store in

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034480#comment-15034480 ] Kuhu Shukla commented on YARN-4406: --- [~rchiang] thank you for reporting this. I think the root cause is:

[jira] [Commented] (YARN-4407) Support Resource oversubscription in YARN scheduler

[ https://issues.apache.org/jira/browse/YARN-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034576#comment-15034576 ] Wangda Tan commented on YARN-4407: -- [~xgong], is this duplicated with YARN-1011/YARN-1013? > Support

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034502#comment-15034502 ] Xuan Gong commented on YARN-4392: - Thanks for Suggestion. [~jlowe] That makes sense. Uploaded a new patch

[jira] [Created] (YARN-4407) Support Resource oversubscription in YARN scheduler

Xuan Gong created YARN-4407: --- Summary: Support Resource oversubscription in YARN scheduler Key: YARN-4407 URL: https://issues.apache.org/jira/browse/YARN-4407 Project: Hadoop YARN Issue Type: New

[jira] [Commented] (YARN-3769) Consider user limit when calculating total pending resource for preemption policy in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034613#comment-15034613 ] Sangjin Lee commented on YARN-3769: --- I'll yield to [~djp] on which version this should make (2.6.3 v.

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034589#comment-15034589 ] Daniel Templeton commented on YARN-4398: Yep. +1 (non-binding) > Yarn recover functionality

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034619#comment-15034619 ] Jian He commented on YARN-4398: --- [~iceberg565], after you upload the patch, you can click the "Submit Patch"

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034490#comment-15034490 ] Ray Chiang commented on YARN-4406: -- Thanks for letting me know. I'll take a look at that. > RM Web UI

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034614#comment-15034614 ] Daniel Templeton commented on YARN-4398: Actually, before I +1 that, [~iceberg565], did you run the

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034647#comment-15034647 ] Ray Chiang commented on YARN-4406: -- So, would the right solution be that getUnuableNodes() should be

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034482#comment-15034482 ] Kuhu Shukla commented on YARN-4406: --- Spoke too soon. on trunk {{updateMetricsForRejoinedNode}} should

[jira] [Assigned] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-4392: --- Assignee: Naganarasimha G R (was: Xuan Gong) > ApplicationCreatedEvent event time

[jira] [Commented] (YARN-4340) Add "list" API to reservation system

[ https://issues.apache.org/jira/browse/YARN-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034792#comment-15034792 ] Subru Krishnan commented on YARN-4340: -- Thanks [~seanpo03] for working on this. Kindly fix the

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034869#comment-15034869 ] Naganarasimha G R commented on YARN-4392: - Hi [~xgong], wrt YARN-4392.2.patch, is it required to

[jira] [Created] (YARN-4408) NodeManager still reports negative running containers

Robert Kanter created YARN-4408: --- Summary: NodeManager still reports negative running containers Key: YARN-4408 URL: https://issues.apache.org/jira/browse/YARN-4408 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3769) Consider user limit when calculating total pending resource for preemption policy in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034784#comment-15034784 ] Junping Du commented on YARN-3769: -- Hi [~sjlee0], given this is non-critical/non-blocker, can we make it

[jira] [Commented] (YARN-4248) REST API for submit/update/delete Reservations

[ https://issues.apache.org/jira/browse/YARN-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035000#comment-15035000 ] Carlo Curino commented on YARN-4248: [~chris.douglas] thanks for the review. I addressed your comments

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Attachment: (was: YARN-4108.poc.1.patch) > CapacityScheduler: Improve preemption to preempt only those

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Attachment: YARN-4108.poc.1.patch > CapacityScheduler: Improve preemption to preempt only those containers

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034766#comment-15034766 ] Wangda Tan commented on YARN-4108: -- Thanks [~eepayne], removed the staled patch and rebased patch to

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

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

[jira] [Commented] (YARN-4392) ApplicationCreatedEvent event time resets after RM restart/failover

[ https://issues.apache.org/jira/browse/YARN-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034843#comment-15034843 ] Naganarasimha G R commented on YARN-4392: - Thanks [~jlowe], bq, If we take that approach I'm

[jira] [Commented] (YARN-3769) Consider user limit when calculating total pending resource for preemption policy in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034897#comment-15034897 ] Sangjin Lee commented on YARN-3769: --- I'm fine with 2.6.4. > Consider user limit when calculating total

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

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

[jira] [Updated] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS

[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3946: Attachment: YARN-3946.v1.005.patch Thanks for the comments [~wangda], bq. When app goes to

[jira] [Assigned] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos reassigned YARN-2883: Assignee: Konstantinos Karanasos > Queuing of container requests in the NM

[jira] [Commented] (YARN-4408) NodeManager still reports negative running containers

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

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035122#comment-15035122 ] Sidharta Seethana commented on YARN-4309: - [~vvasudev] , I took a look at the patch. Couple of

[jira] [Updated] (YARN-4408) NodeManager still reports negative running containers

[ https://issues.apache.org/jira/browse/YARN-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4408: Attachment: YARN-4408.001.patch The patch adds the missing check. It also adds a unit test for this

[jira] [Commented] (YARN-4405) Support node label store in non-appendable file system

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

[jira] [Updated] (YARN-4348) ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding ZK's callback work correctly

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-4348: - Summary: ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding ZK's callback

[jira] [Created] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

Junping Du created YARN-4403: Summary: (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period Key: YARN-4403 URL: https://issues.apache.org/jira/browse/YARN-4403 Project:

[jira] [Commented] (YARN-4348) ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034071#comment-15034071 ] Tsuyoshi Ozawa commented on YARN-4348: -- [~zxu] [~jianhe] I'm rethinking of [this

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034045#comment-15034045 ] Tsuyoshi Ozawa commented on YARN-3798: -- [~jianhe] {quote} If curator sync up the data it would be

[jira] [Updated] (YARN-4348) ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's event thread

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-4348: - Summary: ZKRMStateStore.syncInternal shouldn't wait for sync completion for avoiding blocking ZK's

[jira] [Updated] (YARN-4403) (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating period

[ https://issues.apache.org/jira/browse/YARN-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4403: - Target Version/s: 2.8.0 > (AM/NM/Container)LivelinessMonitor should use monotonic time when calculating >

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035351#comment-15035351 ] Varun Saxena commented on YARN-3862: Thanks Sangjin for the review and commit. Thanks Li and Joep for

[jira] [Updated] (YARN-4333) Fair scheduler should support preemption within queue

[ https://issues.apache.org/jira/browse/YARN-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Yuan updated YARN-4333: Issue Type: Improvement (was: Bug) > Fair scheduler should support preemption within queue >

[jira] [Updated] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3862: --- Attachment: (was: YARN-3862-feature-YARN-2928.05.patch) > Support for fetching specific configs

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035308#comment-15035308 ] Sangjin Lee commented on YARN-3862: --- They do need to be fixed (sooner than later), but I'm OK with

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035315#comment-15035315 ] Varun Saxena commented on YARN-3862: Filed YARN-4409 > Support for fetching specific configs and

[jira] [Created] (YARN-4409) Fix javadoc and checkstyle issues in timelineservice code

Varun Saxena created YARN-4409: -- Summary: Fix javadoc and checkstyle issues in timelineservice code Key: YARN-4409 URL: https://issues.apache.org/jira/browse/YARN-4409 Project: Hadoop YARN

[jira] [Commented] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

[ https://issues.apache.org/jira/browse/YARN-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035223#comment-15035223 ] Naganarasimha G R commented on YARN-4406: - Hi [~rchiang] & [~kshukla] YARN-3102 also is for the

[jira] [Commented] (YARN-3417) AM to be able to exit with a request saying "restart me with these (possibly updated) resource requirements"

[ https://issues.apache.org/jira/browse/YARN-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035246#comment-15035246 ] Varun Saxena commented on YARN-3417: Thanks Steve for the clarification. > AM to be able to exit with

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

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

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035275#comment-15035275 ] Varun Saxena commented on YARN-3862: [~sjlee0], kindly review. Regarding some of the checkstyle

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035302#comment-15035302 ] Rohith Sharma K S commented on YARN-4164: - I think just log message update with clarity should be

[jira] [Updated] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3862: --- Attachment: YARN-3862-feature-YARN-2928.005.patch Renamed patch to try and invoke Jenkins > Support

[jira] [Commented] (YARN-4292) ResourceUtilization should be a part of NodeInfo REST API

[ https://issues.apache.org/jira/browse/YARN-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035250#comment-15035250 ] Sunil G commented on YARN-4292: --- Test case failures are known except for TestApplicationPriority and

[jira] [Commented] (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:comment-tabpanel=15035254#comment-15035254 ] Rohith Sharma K S commented on YARN-4401: - bq. if a job is stored with a resource allocation that

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035274#comment-15035274 ] Sunil G commented on YARN-4164: --- Thanks [~rohithsharma] for updating the patch. {code} Priority

[jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS

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

[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035310#comment-15035310 ] Varun Saxena commented on YARN-3862: Ok...Will do so. > Support for fetching specific configs and

[jira] [Updated] (YARN-4395) Typo in comment in ClientServiceDelegate

[ https://issues.apache.org/jira/browse/YARN-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4395: --- Assignee: Devon Michaels (was: Daniel Templeton) > Typo in comment in ClientServiceDelegate >

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

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

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034353#comment-15034353 ] Wangda Tan commented on YARN-4108: -- Thanks for sharing your thoughts, [~bikassaha]! I've done a POC very

[jira] [Created] (YARN-4405) Support node label store in non-appendable file system

Wangda Tan created YARN-4405: Summary: Support node label store in non-appendable file system Key: YARN-4405 URL: https://issues.apache.org/jira/browse/YARN-4405 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4390) Consider container request size during CS preemption

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034376#comment-15034376 ] Wangda Tan commented on YARN-4390: -- Thanks for sharing your thoughts, [~curino]! I agree with most of

[jira] [Commented] (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:comment-tabpanel=15034399#comment-15034399 ] Daniel Templeton commented on YARN-4401: There are lots of reasons a recovery could fail. For

[jira] [Updated] (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 updated YARN-4401: --- Attachment: YARN-4401.001.patch Here's the basic idea of what I'm proposing. > A failed app

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Attachment: YARN-4108.poc.1.patch > CapacityScheduler: Improve preemption to preempt only those containers

[jira] [Updated] (YARN-4404) Typo in comment in SchedulerUtils

[ https://issues.apache.org/jira/browse/YARN-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4404: --- Assignee: Devon Michaels (was: Daniel Templeton) > Typo in comment in SchedulerUtils >

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034346#comment-15034346 ] Wangda Tan commented on YARN-4108: -- Uploading design doc with initial POC patch for review. I put general

[jira] [Created] (YARN-4404) Typo in comment in SchedulerUtils

Daniel Templeton created YARN-4404: -- Summary: Typo in comment in SchedulerUtils Key: YARN-4404 URL: https://issues.apache.org/jira/browse/YARN-4404 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Attachment: YARN-4108-design-doc-v1.pdf > CapacityScheduler: Improve preemption to preempt only those

[jira] [Updated] (YARN-4404) Typo in comment in SchedulerUtils

[ https://issues.apache.org/jira/browse/YARN-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-4404: --- Issue Type: Improvement (was: Bug) > Typo in comment in SchedulerUtils >

[jira] [Updated] (YARN-3769) Consider user limit when calculating total pending resource for preemption policy in Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-3769: - Attachment: YARN-3769-branch-2.6.001.patch Attaching {{YARN-3769-branch-2.6.001.patch}} for backport to

[jira] [Created] (YARN-4406) RM Web UI continues to show decommissioned nodes even after RM restart

Ray Chiang created YARN-4406: Summary: RM Web UI continues to show decommissioned nodes even after RM restart Key: YARN-4406 URL: https://issues.apache.org/jira/browse/YARN-4406 Project: Hadoop YARN

[jira] [Commented] (YARN-4398) Yarn recover functionality causes the cluster running slowly and the cluster usage rate is far below 100

[ https://issues.apache.org/jira/browse/YARN-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034466#comment-15034466 ] Jian He commented on YARN-4398: --- patch looks good to me. thanks [~iceberg565], and [~templedf] for the

[jira] [Updated] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4164: Attachment: 0003-YARN-4164.patch Updated the patch fixing review comment that null will not

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

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

[jira] [Commented] (YARN-3417) AM to be able to exit with a request saying "restart me with these (possibly updated) resource requirements"

[ https://issues.apache.org/jira/browse/YARN-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033454#comment-15033454 ] Steve Loughran commented on YARN-3417: -- For Slider, we are coping with things today (and fixed

[jira] [Updated] (YARN-4328) Findbugs warning in resourcemanager in branch-2.7 and branch-2.6

[ https://issues.apache.org/jira/browse/YARN-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4328: Attachment: YARN-4328.branch-2.6.00.patch > Findbugs warning in resourcemanager in branch-2.7 and

[jira] [Commented] (YARN-4328) Findbugs warning in resourcemanager in branch-2.7 and branch-2.6

[ https://issues.apache.org/jira/browse/YARN-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033309#comment-15033309 ] Akira AJISAKA commented on YARN-4328: - I'm thinking it's okay to add a section in findbugs-exclude.xml

[jira] [Commented] (YARN-3456) Improve handling of incomplete TimelineEntities

[ https://issues.apache.org/jira/browse/YARN-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033486#comment-15033486 ] Rohith Sharma K S commented on YARN-3456: - +1 lgtm.. > Improve handling of incomplete

[jira] [Commented] (YARN-3456) Improve handling of incomplete TimelineEntities

[ https://issues.apache.org/jira/browse/YARN-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033488#comment-15033488 ] Rohith Sharma K S commented on YARN-3456: - I will wait for a day before committing it. > Improve

[jira] [Updated] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3862: --- Attachment: YARN-3862-feature-YARN-2928.05.patch > Support for fetching specific configs and metrics

[jira] [Updated] (YARN-4292) ResourceUtilization should be a part of NodeInfo REST API

[ https://issues.apache.org/jira/browse/YARN-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4292: -- Attachment: 0005-YARN-4292.patch Thank you [~leftnoteasy] for the comments. Yes, I also agree with your

[jira] [Created] (YARN-4402) TestNodeManagerShutdown And TestNodeManagerResync fails with bind exception

Brahma Reddy Battula created YARN-4402: -- Summary: TestNodeManagerShutdown And TestNodeManagerResync fails with bind exception Key: YARN-4402 URL: https://issues.apache.org/jira/browse/YARN-4402

[jira] [Commented] (YARN-4348) ZKRMStateStore.syncInternal should wait for zkResyncWaitTime instead of zkSessionTimeout

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033915#comment-15033915 ] Tsuyoshi Ozawa commented on YARN-4348: -- Ran test since last Jenkins failed to launch. javadoc seems to

[jira] [Updated] (YARN-4402) TestNodeManagerShutdown And TestNodeManagerResync fails with bind exception

[ https://issues.apache.org/jira/browse/YARN-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-4402: --- Attachment: YARN-4402.patch > TestNodeManagerShutdown And TestNodeManagerResync fails

[jira] [Commented] (YARN-4348) ZKRMStateStore.syncInternal should wait for zkResyncWaitTime instead of zkSessionTimeout

[ https://issues.apache.org/jira/browse/YARN-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033937#comment-15033937 ] Junping Du commented on YARN-4348: -- Hi [~ozawa] and [~jianhe], is this a blocker bug? Can we move it to

[jira] [Commented] (YARN-1848) Persist ClusterMetrics across RM HA transitions

[ https://issues.apache.org/jira/browse/YARN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033756#comment-15033756 ] Junping Du commented on YARN-1848: -- Moving it to 2.6.4 as no update on this JIRA for a while. > Persist

[jira] [Updated] (YARN-1767) Windows: Allow a way for users to augment classpath of YARN daemons

[ https://issues.apache.org/jira/browse/YARN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1767: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > Windows: Allow a way for users to augment classpath

[jira] [Updated] (YARN-2457) FairScheduler: Handle preemption to help starved parent queues

[ https://issues.apache.org/jira/browse/YARN-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2457: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > FairScheduler: Handle preemption to help starved

[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 ] Junping Du updated YARN-3478: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > FairScheduler page not performed because different

[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-tabpanel=15033763#comment-15033763 ] Junping Du commented on YARN-3478: -- Move it to 2.6.4 as no update on this JIRA for a while. >

[jira] [Commented] (YARN-1767) Windows: Allow a way for users to augment classpath of YARN daemons

[ https://issues.apache.org/jira/browse/YARN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033761#comment-15033761 ] Junping Du commented on YARN-1767: -- Move it to 2.6.4 as no update on this JIRA for a while. > Windows:

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033765#comment-15033765 ] Junping Du commented on YARN-1480: -- Move it to 2.6.4 as no update on JIRA for a while. > RM web services

[jira] [Updated] (YARN-2037) Add restart support for Unmanaged AMs

[ https://issues.apache.org/jira/browse/YARN-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2037: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > Add restart support for Unmanaged AMs >

[jira] [Updated] (YARN-2599) Standby RM should also expose some jmx and metrics

[ https://issues.apache.org/jira/browse/YARN-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2599: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > Standby RM should also expose some jmx and metrics >

[jira] [Commented] (YARN-2457) FairScheduler: Handle preemption to help starved parent queues

[ https://issues.apache.org/jira/browse/YARN-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033757#comment-15033757 ] Junping Du commented on YARN-2457: -- Move it to 2.6.4 as no update on this jira for a while. >

[jira] [Updated] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1480: - Target Version/s: 2.7.3, 2.6.4 (was: 2.6.3, 2.7.3) > RM web services getApps() accepts many more filters

[jira] [Commented] (YARN-2037) Add restart support for Unmanaged AMs

[ https://issues.apache.org/jira/browse/YARN-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033771#comment-15033771 ] Junping Du commented on YARN-2037: -- Move it to 2.6.4 as no update on this JIRA for a while. > Add restart

  1   2   >