[jira] [Commented] (YARN-4794) Deadlock in NMClientImpl

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

[jira] [Comment Edited] (YARN-4794) Deadlock in NMClientImpl

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236574#comment-15236574 ] Rohith Sharma K S edited comment on YARN-4794 at 4/12/16 4:47 AM: --

[jira] [Commented] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236575#comment-15236575 ] Bibin A Chundatt commented on YARN-4909: {quote} One question is, why set of failure cases are

[jira] [Commented] (YARN-4794) Deadlock in NMClientImpl

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236574#comment-15236574 ] Rohith Sharma K S commented on YARN-4794: - Committed to trunk/branch-2/branch-2.8 Patch do apply in

[jira] [Commented] (YARN-4939) the decommissioning Node should keep alive if NM restart

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

[jira] [Updated] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4909: --- Attachment: 0004-YARN-4909.patch Attaching patch after rm test change > Fix intermittent

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

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

[jira] [Commented] (YARN-4794) Deadlock in NMClientImpl

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236542#comment-15236542 ] Rohith Sharma K S commented on YARN-4794: - +1 lgtm, will commit it.. > Deadlock in NMClientImpl >

[jira] [Updated] (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 updated YARN-2883: - Attachment: YARN-2883-trunk.011.patch Re-attaching the patch (there was a problem

[jira] [Updated] (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 updated YARN-2883: - Attachment: (was: YARN-2883-trunk.011.patch) > Queuing of container requests

[jira] [Commented] (YARN-4807) MockAM#waitForState sleep duration is too long

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

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

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

[jira] [Updated] (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 updated YARN-2883: - Attachment: YARN-2883-trunk.011.patch [~kasha], thanks for the review. I am

[jira] [Commented] (YARN-2567) Add a percentage-node threshold for RM to wait for new allocations after restart/failover

[ https://issues.apache.org/jira/browse/YARN-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236459#comment-15236459 ] sandflee commented on YARN-2567: Hi , [~vinodkv], could you assign this to me, I'd like to work on this.

[jira] [Commented] (YARN-4794) Deadlock in NMClientImpl

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

[jira] [Updated] (YARN-4946) RM should write out Aggregated Log Completion file flag next to logs

[ https://issues.apache.org/jira/browse/YARN-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4946: Description: MAPREDUCE-6415 added a tool that combines the aggregated log files for each Yarn App

[jira] [Commented] (YARN-4946) RM should write out Aggregated Log Completion file flag next to logs

[ https://issues.apache.org/jira/browse/YARN-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236442#comment-15236442 ] Robert Kanter commented on YARN-4946: - [~jlowe], [~kasha], thoughts? > RM should write out Aggregated

[jira] [Created] (YARN-4946) RM should write out Aggregated Log Completion file flag next to logs

Robert Kanter created YARN-4946: --- Summary: RM should write out Aggregated Log Completion file flag next to logs Key: YARN-4946 URL: https://issues.apache.org/jira/browse/YARN-4946 Project: Hadoop YARN

[jira] [Updated] (YARN-4939) the decommissioning Node should keep alive if NM restart

[ https://issues.apache.org/jira/browse/YARN-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4939: --- Attachment: YARN-4939.02.patch > the decommissioning Node should keep alive if NM restart >

[jira] [Updated] (YARN-4939) the decommissioning Node should keep alive if NM restart

[ https://issues.apache.org/jira/browse/YARN-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4939: --- Attachment: (was: YARN-4939.02.patch) > the decommissioning Node should keep alive if NM restart >

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236422#comment-15236422 ] Robert Kanter commented on YARN-4676: - Sorry for taking so long to review the updated patch. Thanks

[jira] [Commented] (YARN-4939) the decommissioning Node should keep alive if NM restart

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

[jira] [Updated] (YARN-4939) the decommissioning Node should keep alive if NM restart

[ https://issues.apache.org/jira/browse/YARN-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4939: --- Attachment: YARN-4939.02.patch ./bin/yarn node -list -states DECOMMISSIONING couldn't get the

[jira] [Updated] (YARN-4929) Fix test failures because of removing the minimum wait time for attempts.

[ https://issues.apache.org/jira/browse/YARN-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4929: --- Attachment: YARN-4929.001.patch This patch depends on YARN-4807. So I didn't push the "Submit Patch" button

[jira] [Updated] (YARN-4929) Fix test failures because of removing the minimum wait time for attempts.

[ https://issues.apache.org/jira/browse/YARN-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4929: --- Summary: Fix test failures because of removing the minimum wait time for attempts. (was: Fix test failures

[jira] [Updated] (YARN-4929) Fix test failures because of removing the minimum wait time for attempt.

[ https://issues.apache.org/jira/browse/YARN-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4929: --- Summary: Fix test failures because of removing the minimum wait time for attempt. (was: Fix unit test case

[jira] [Commented] (YARN-4911) Bad placement policy in FairScheduler causes the RM to crash

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

[jira] [Updated] (YARN-4807) MockAM#waitForState sleep duration is too long

[ https://issues.apache.org/jira/browse/YARN-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4807: --- Attachment: YARN-4807.008.patch I uploaded a new patch since one recent commit used the old code. >

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236305#comment-15236305 ] Wangda Tan commented on YARN-4945: -- Some rough ideas about design: In general, after YARN-4822, we can

[jira] [Commented] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236287#comment-15236287 ] Wangda Tan commented on YARN-2113: -- [~eepayne], [~sunilg]. I planned to work on YARN-4781 soon but I'm

[jira] [Updated] (YARN-4781) Support intra-queue preemption for fairness ordering policy.

[ https://issues.apache.org/jira/browse/YARN-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4781: - Issue Type: Sub-task (was: Bug) Parent: YARN-4945 > Support intra-queue preemption for fairness

[jira] [Updated] (YARN-4781) Support intra-queue preemption for fairness ordering policy.

[ https://issues.apache.org/jira/browse/YARN-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4781: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-3306) > Support intra-queue preemption for

[jira] [Updated] (YARN-2009) Priority support for preemption in ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2009: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-1963) > Priority support for preemption in

[jira] [Updated] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2113: - Issue Type: Sub-task (was: Bug) Parent: YARN-4945 > Add cross-user preemption within

[jira] [Updated] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2113: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-45) > Add cross-user preemption within

[jira] [Created] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

Wangda Tan created YARN-4945: Summary: [Umbrella] Capacity Scheduler Preemption Within a queue Key: YARN-4945 URL: https://issues.apache.org/jira/browse/YARN-4945 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236270#comment-15236270 ] Wangda Tan commented on YARN-4909: -- Thanks [~brahmareddy] for reporting this and thanks [~bibinchundatt]

[jira] [Updated] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4909: - Priority: Blocker (was: Major) > Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[jira] [Commented] (YARN-3452) Bogus token usernames cause many invalid group lookups

[ https://issues.apache.org/jira/browse/YARN-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236192#comment-15236192 ] Vinod Kumar Vavilapalli commented on YARN-3452: --- Old JIRA. bq. However YARN really should

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

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

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236128#comment-15236128 ] sandflee commented on YARN-4924: Thanks [~jlowe], not noticed that DBException is a RUNTIME exception,

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236117#comment-15236117 ] Jason Lowe commented on YARN-4924: -- org.iq80.levedb.DBException (the one we're interested in catching) is

[jira] [Updated] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4924: --- Attachment: YARN-4924.04.patch > NM recovery race can lead to container not cleaned up >

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236115#comment-15236115 ] sandflee commented on YARN-4924: in case of createWriteBatch throws runtime Exception, seems more safer to

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236072#comment-15236072 ] sandflee commented on YARN-4924: >From the interface of DB, createWriteBatch didn't not throw exception.

[jira] [Updated] (YARN-4911) Bad placement policy in FairScheduler causes the RM to crash

[ https://issues.apache.org/jira/browse/YARN-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-4911: - Attachment: YARN-4911.002.patch - Modify unit test to verify exception occurs > Bad placement policy in

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

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

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236015#comment-15236015 ] Jason Lowe commented on YARN-4924: -- Thanks for updating the patch! cleanupKeysWithPrefix can now let the

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

[ https://issues.apache.org/jira/browse/YARN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236004#comment-15236004 ] Li Lu commented on YARN-4886: - [~xgong], since this patch has been pending for a few days and Jenkins finally

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

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

[jira] [Commented] (YARN-4886) Add HDFS caller context for EntityGroupFSTimelineStore

[ https://issues.apache.org/jira/browse/YARN-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235960#comment-15235960 ] Li Lu commented on YARN-4886: - OK, I don't know why this JIRA keeps being ignored by Jenkins. I manually

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

[jira] [Created] (YARN-4944) Handle lack of ResourceCalculatorPlugin gracefully

Karthik Kambatla created YARN-4944: -- Summary: Handle lack of ResourceCalculatorPlugin gracefully Key: YARN-4944 URL: https://issues.apache.org/jira/browse/YARN-4944 Project: Hadoop YARN

[jira] [Commented] (YARN-4784) fair scheduler: defaultQueueSchedulingPolicy should not accept fifo as a value

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

[jira] [Commented] (YARN-4168) Test TestLogAggregationService.testLocalFileDeletionOnDiskFull failing

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

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

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234184#comment-15234184 ] Karthik Kambatla edited comment on YARN-2883 at 4/11/16 7:22 PM: - Thanks

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

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234184#comment-15234184 ] Karthik Kambatla edited comment on YARN-2883 at 4/11/16 7:23 PM: - Thanks

[jira] [Commented] (YARN-1297) Miscellaneous Fair Scheduler speedups

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

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235712#comment-15235712 ] Jonathan Maron commented on YARN-4757: -- thanks! I believe I'll need to be voted on as a branch

[jira] [Commented] (YARN-3863) Support complex filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235697#comment-15235697 ] Sangjin Lee commented on YARN-3863: --- The latest patch LGTM. I'd like to wait until the end of day today

[jira] [Commented] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235629#comment-15235629 ] Sunil G commented on YARN-2113: --- Hi [~eepayne] I have done some work in YARN-2009 as prototype, but based on

[jira] [Commented] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235611#comment-15235611 ] Eric Payne commented on YARN-2113: -- {quote} Vinod Kumar Vavilapalli, have you had any chance to think

[jira] [Assigned] (YARN-4890) Unit test intermittent failure: TestNodeLabelContainerAllocation#testQueueUsedCapacitiesUpdate

[ https://issues.apache.org/jira/browse/YARN-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-4890: - Assignee: Sunil G > Unit test intermittent failure: >

[jira] [Commented] (YARN-4931) Preempted resources go back to the same application

[ https://issues.apache.org/jira/browse/YARN-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235591#comment-15235591 ] Miles Crawford commented on YARN-4931: -- If it is helpful, it looks like these applications have a huge

[jira] [Comment Edited] (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=15235552#comment-15235552 ] Wangda Tan edited comment on YARN-3215 at 4/11/16 5:31 PM: --- [~Naganarasimha],

[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=15235552#comment-15235552 ] Wangda Tan commented on YARN-3215: -- [~Naganarasimha], hopefully no if Jenkins came back with +1. :) >

[jira] [Updated] (YARN-4794) Deadlock in NMClientImpl

[ https://issues.apache.org/jira/browse/YARN-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4794: -- Attachment: YARN-4794.2.patch thanks for the reviews, removed that duplicate call > Deadlock in NMClientImpl >

[jira] [Updated] (YARN-4935) TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4935: --- Attachment: YARN-4935.002.patch > TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler >

[jira] [Commented] (YARN-4935) TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235494#comment-15235494 ] Yufei Gu commented on YARN-4935: Thanks [~kasha] for the review. Its goal is to test YarnClient behavior.

[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=15235480#comment-15235480 ] Naganarasimha G R commented on YARN-3215: - Thanks for the review and the commit [~wangda], bq.

[jira] [Updated] (YARN-4941) Dump container metrics to a log file at the end of the container's lifecycle when log-container-debug-info is enabled

[ https://issues.apache.org/jira/browse/YARN-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4941: Summary: Dump container metrics to a log file at the end of the container's lifecycle when

[jira] [Commented] (YARN-4941) Dump container metrics to a log file at the end of the container's lifecycle when log-container-debug-info is enabled

[ https://issues.apache.org/jira/browse/YARN-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235476#comment-15235476 ] Varun Vasudev commented on YARN-4941: - I'd like to be able to see the container metrics as part of the

[jira] [Commented] (YARN-4941) Dump container metrics to a log file when log-container-debug-info is enabled

[ https://issues.apache.org/jira/browse/YARN-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235458#comment-15235458 ] Daniel Templeton commented on YARN-4941: If you want to dump the container metrics to log files you

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

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

[jira] [Commented] (YARN-2113) Add cross-user preemption within CapacityScheduler's leaf-queue

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235451#comment-15235451 ] Eric Payne commented on YARN-2113: -- [~vinodkv], have you had any chance to think about the implementation

[jira] [Updated] (YARN-4907) Make all MockRM#waitForState consistent.

[ https://issues.apache.org/jira/browse/YARN-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4907: --- Description: There are some inconsistencies among these {{waitForState}} in {{MockRM}}: 1. Some

[jira] [Updated] (YARN-4907) Make all MockRM#waitForState consistent.

[ https://issues.apache.org/jira/browse/YARN-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-4907: --- Description: There are some inconsistencies among these {{waitForState}} in {{MockRM}}: 1. Some

[jira] [Updated] (YARN-4514) [YARN-3368] Cleanup hardcoded configurations, such as RM/ATS addresses

[ https://issues.apache.org/jira/browse/YARN-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4514: -- Attachment: YARN-4514-YARN-3368.5.patch [~leftnoteasy] and [~varun_saxena] I have made some more changes in

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

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

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

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

[jira] [Commented] (YARN-4940) yarn node -list -all failed if RM start with decommissioned node

[ https://issues.apache.org/jira/browse/YARN-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235388#comment-15235388 ] sandflee commented on YARN-4940: seems not, they are all caused by YARN-3102 > yarn node -list -all failed

[jira] [Updated] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sandflee updated YARN-4924: --- Attachment: YARN-4924.03.patch > NM recovery race can lead to container not cleaned up >

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235358#comment-15235358 ] Jason Lowe commented on YARN-4311: -- If we only remove truly untracked nodes then option 1 should be OK.

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235369#comment-15235369 ] sandflee commented on YARN-4924: thanks [~jlowe], I added @Deprecated to FINISHED_APP_KEY_PREFIX, but

[jira] [Updated] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-4311: - Target Version/s: 2.8.0, 2.7.4 Fix Version/s: (was: 2.8.0) I reverted this from trunk,

[jira] [Commented] (YARN-4928) Some yarn.server.timeline.* tests fail on Windows attempting to use a test root path containing a colon

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

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235331#comment-15235331 ] Jason Lowe commented on YARN-4311: -- No need for a followup JIRA, I'll revert the one in trunk until we

[jira] [Created] (YARN-4943) Add support to collect actual resource usage from cgroups

Varun Vasudev created YARN-4943: --- Summary: Add support to collect actual resource usage from cgroups Key: YARN-4943 URL: https://issues.apache.org/jira/browse/YARN-4943 Project: Hadoop YARN

[jira] [Created] (YARN-4942) Dump timeline of container state transitions when log-container-debug-info is enabled

Varun Vasudev created YARN-4942: --- Summary: Dump timeline of container state transitions when log-container-debug-info is enabled Key: YARN-4942 URL: https://issues.apache.org/jira/browse/YARN-4942

[jira] [Created] (YARN-4941) Dump container metrics to a log file when log-container-debug-info is enabled

Varun Vasudev created YARN-4941: --- Summary: Dump container metrics to a log file when log-container-debug-info is enabled Key: YARN-4941 URL: https://issues.apache.org/jira/browse/YARN-4941 Project:

[jira] [Commented] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235312#comment-15235312 ] Varun Vasudev commented on YARN-4876: - bq. I tend to agree with you, but my intention was to introduce

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235307#comment-15235307 ] Kuhu Shukla commented on YARN-4311: --- The problem does exist. In a scenario where the node being removed

[jira] [Commented] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

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

[jira] [Updated] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3998: --- Attachment: YARN-3998.09.patch > Add retry-times to let NM re-launch container when it fails to run >

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235213#comment-15235213 ] Jun Gong commented on YARN-3998: Thanks [~vvasudev] for the review and comments! Attach a rebased patch

[jira] [Commented] (YARN-4924) NM recovery race can lead to container not cleaned up

[ https://issues.apache.org/jira/browse/YARN-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235212#comment-15235212 ] Jason Lowe commented on YARN-4924: -- Thanks for updating the patch! It may not be clear to others reading

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235181#comment-15235181 ] Kuhu Shukla commented on YARN-4311: --- Thank you [~jlowe] for the comments. The final variables and the

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235166#comment-15235166 ] Jason Lowe commented on YARN-4311: -- Thanks for updating the patch! Couple of comments: The patch has a

[jira] [Updated] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4909: --- Attachment: 0003-YARN-4909.patch Earlier for {{JerseyTest.init<>}} was using always the

[jira] [Commented] (YARN-3971) Skip RMNodeLabelsManager#checkRemoveFromClusterNodeLabelsOfQueue on nodelabel recovery

[ https://issues.apache.org/jira/browse/YARN-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235069#comment-15235069 ] Bibin A Chundatt commented on YARN-3971: Testcase failures are already tracked as part of YARN-4909

  1   2   >