[jira] [Commented] (YARN-2298) Move TimelineClient to yarn-common

[ https://issues.apache.org/jira/browse/YARN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074145#comment-14074145 ] Zhijie Shen commented on YARN-2298: --- I agree this is not an idea solution to split a

[jira] [Commented] (YARN-641) Make AMLauncher in RM Use NMClient

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

[jira] [Commented] (YARN-2347) Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in yarn-server-common

[ https://issues.apache.org/jira/browse/YARN-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074198#comment-14074198 ] Zhijie Shen commented on YARN-2347: --- [~djp], it's a good idea to refactor the code to

[jira] [Commented] (YARN-2347) Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in yarn-server-common

[ https://issues.apache.org/jira/browse/YARN-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074204#comment-14074204 ] Zhijie Shen commented on YARN-2347: --- Please ignore previous comment 1. I posted the wrong

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074249#comment-14074249 ] Wangda Tan commented on YARN-2069: -- Hi [~mayank_bansal], Thanks for working on this again.

[jira] [Commented] (YARN-2336) Fair scheduler REST api returns a missing '[' bracket JSON for deep queue tree

[ https://issues.apache.org/jira/browse/YARN-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074268#comment-14074268 ] Akira AJISAKA commented on YARN-2336: - Thanks [~kj-ki] for the update. +1

[jira] [Created] (YARN-2356) yarn status command for non-existent application/application attempt/container is too verbose

Sunil G created YARN-2356: - Summary: yarn status command for non-existent application/application attempt/container is too verbose Key: YARN-2356 URL: https://issues.apache.org/jira/browse/YARN-2356

[jira] [Updated] (YARN-2356) yarn status command for non-existent application/application attempt/container is too verbose

[ https://issues.apache.org/jira/browse/YARN-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2356: -- Attachment: Yarn-2356.1.patch Fixed to handle ApplicationNotFoundException,

[jira] [Created] (YARN-2357) Port Windows Secure Container Executor YARN-1063, YARN-1972, YARN-2198 changes to branch-2

Remus Rusanu created YARN-2357: -- Summary: Port Windows Secure Container Executor YARN-1063, YARN-1972, YARN-2198 changes to branch-2 Key: YARN-2357 URL: https://issues.apache.org/jira/browse/YARN-2357

[jira] [Updated] (YARN-2357) Port Windows Secure Container Executor YARN-1063, YARN-1972, YARN-2198 changes to branch-2

[ https://issues.apache.org/jira/browse/YARN-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2357: --- Attachment: YARN-2357.1.patch Patch .1 is port of currently uploaded YARN-1063 .6, YARN-1972 .3 and

[jira] [Updated] (YARN-2357) Port Windows Secure Container Executor YARN-1063, YARN-1972, YARN-2198 changes to branch-2

[ https://issues.apache.org/jira/browse/YARN-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2357: --- Attachment: YARN-2357.1.patch Now with compile fix! Port Windows Secure Container Executor

[jira] [Commented] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074366#comment-14074366 ] Rohith commented on YARN-2209: -- Hi [~jianhe], I reviewed patch and found some comments 1.

[jira] [Commented] (YARN-2214) preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074509#comment-14074509 ] Karthik Kambatla commented on YARN-2214: +1. Checking this in.

[jira] [Updated] (YARN-2214) FairScheduler: preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2214: --- Issue Type: Improvement (was: Bug) FairScheduler: preemptContainerPreCheck() in

[jira] [Updated] (YARN-2214) FairScheduler: preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2214: --- Summary: FairScheduler: preemptContainerPreCheck() in FSParentQueue delays convergence

[jira] [Created] (YARN-2358) TestNamenodeCapacityReport.testXceiverCount may sometimes fail due to lack of retry

Mit Desai created YARN-2358: --- Summary: TestNamenodeCapacityReport.testXceiverCount may sometimes fail due to lack of retry Key: YARN-2358 URL: https://issues.apache.org/jira/browse/YARN-2358 Project:

[jira] [Commented] (YARN-1354) Recover applications upon nodemanager restart

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

[jira] [Commented] (YARN-2214) FairScheduler: preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

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

[jira] [Commented] (YARN-2214) FairScheduler: preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074548#comment-14074548 ] Ashwin Shankar commented on YARN-2214: -- Thanks Karthik ! FairScheduler:

[jira] [Created] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

zhihai xu created YARN-2359: --- Summary: Application is hung without timeout and retry after DNS/network is down. Key: YARN-2359 URL: https://issues.apache.org/jira/browse/YARN-2359 Project: Hadoop YARN

[jira] [Updated] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

[ https://issues.apache.org/jira/browse/YARN-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2359: Priority: Critical (was: Major) Application is hung without timeout and retry after DNS/network is down.

[jira] [Commented] (YARN-2335) Annotate all hadoop-sls APIs as @Private

[ https://issues.apache.org/jira/browse/YARN-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074593#comment-14074593 ] Karthik Kambatla commented on YARN-2335: +1 Annotate all hadoop-sls APIs as

[jira] [Commented] (YARN-2335) Annotate all hadoop-sls APIs as @Private

[ https://issues.apache.org/jira/browse/YARN-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074600#comment-14074600 ] Karthik Kambatla commented on YARN-2335: Committed to trunk. branch-2 had

[jira] [Updated] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

[ https://issues.apache.org/jira/browse/YARN-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2211: -- Attachment: YARN-2211.8.patch Looks good overall, fixed some log msgs myself. re-submit the patch.

[jira] [Commented] (YARN-2335) Annotate all hadoop-sls APIs as @Private

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

[jira] [Updated] (YARN-2335) Annotate all hadoop-sls APIs as @Private

[ https://issues.apache.org/jira/browse/YARN-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2335: -- Attachment: YARN-2335-1.branch2.patch update patch for branch-2 Annotate all hadoop-sls APIs as @Private

[jira] [Commented] (YARN-2335) Annotate all hadoop-sls APIs as @Private

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

[jira] [Commented] (YARN-2262) Few fields displaying wrong values in Timeline server after RM restart

[ https://issues.apache.org/jira/browse/YARN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074636#comment-14074636 ] Zhijie Shen commented on YARN-2262: --- [~nishan], thanks for sharing the logs. I've done a

[jira] [Commented] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074635#comment-14074635 ] Anubhav Dhoot commented on YARN-2229: - We cannot simply add a field and have old code

[jira] [Commented] (YARN-2262) Few fields displaying wrong values in Timeline server after RM restart

[ https://issues.apache.org/jira/browse/YARN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074677#comment-14074677 ] Zhijie Shen commented on YARN-2262: --- [~nishan] and [~Naganarasimha], I've a general

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726-6.patch rebase the patch after YARN-2335. May not work with branch-2, will update a

[jira] [Commented] (YARN-1354) Recover applications upon nodemanager restart

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

[jira] [Commented] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

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

[jira] [Updated] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

[ https://issues.apache.org/jira/browse/YARN-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2211: Attachment: YARN-2211.8.1.patch RMStateStore needs to save AMRMToken master key for recovery when RM

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

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

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726-6-branch2.patch update a patch for branch2 ResourceSchedulerWrapper failed due to the

[jira] [Updated] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

[ https://issues.apache.org/jira/browse/YARN-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2359: Attachment: YARN-2359.000.patch Application is hung without timeout and retry after DNS/network is down.

[jira] [Commented] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

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

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

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

[jira] [Commented] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

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

[jira] [Commented] (YARN-2211) RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens

[ https://issues.apache.org/jira/browse/YARN-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074876#comment-14074876 ] Jian He commented on YARN-2211: --- looks good, +1 RMStateStore needs to save AMRMToken master

[jira] [Updated] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

[ https://issues.apache.org/jira/browse/YARN-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2359: Description: Application is hung without timeout and retry after DNS/network is down. It is because right

[jira] [Updated] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

[ https://issues.apache.org/jira/browse/YARN-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2359: Description: Application is hung without timeout and retry after DNS/network is down. It is because right

[jira] [Updated] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

[ https://issues.apache.org/jira/browse/YARN-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2212: Attachment: YARN-2212.3.patch Adding more testcases ApplicationMaster needs to find a way to update the

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074940#comment-14074940 ] Mayank Bansal commented on YARN-2069: - HI [~wangda] , Thanks for the review. Let me

[jira] [Updated] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2026: - Attachment: YARN-2026-v3.txt Fair scheduler : Fair share for inactive queues causes unfair

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074989#comment-14074989 ] Karthik Kambatla commented on YARN-1726: Comments on the trunk patch: #

[jira] [Updated] (YARN-2359) Application is hung without timeout and retry after DNS/network is down.

[ https://issues.apache.org/jira/browse/YARN-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2359: Description: Application is hung without timeout and retry after DNS/network is down. It is because right

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075011#comment-14075011 ] Ashwin Shankar commented on YARN-2026: -- Incorporated [~kasha] suggestion of having two

[jira] [Updated] (YARN-1707) Making the CapacityScheduler more dynamic

[ https://issues.apache.org/jira/browse/YARN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-1707: --- Attachment: YARN-1707.patch Making the CapacityScheduler more dynamic

[jira] [Commented] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

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

[jira] [Commented] (YARN-1707) Making the CapacityScheduler more dynamic

[ https://issues.apache.org/jira/browse/YARN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075076#comment-14075076 ] Carlo Curino commented on YARN-1707: The attached patch is part of the YARN-1051

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

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

[jira] [Commented] (YARN-1707) Making the CapacityScheduler more dynamic

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

[jira] [Updated] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2209: -- Attachment: YARN-2209.4.patch Replace allocate#resync command with ApplicationMasterNotRegisteredException

[jira] [Updated] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

[ https://issues.apache.org/jira/browse/YARN-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2212: Attachment: YARN-2212.3.1.patch ApplicationMaster needs to find a way to update the AMRMToken periodically

[jira] [Commented] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

[ https://issues.apache.org/jira/browse/YARN-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075125#comment-14075125 ] Jian He commented on YARN-2209: --- Thanks for the review, Rohith. Uploaded a new patch which

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726-7.patch Update a patch to fix the comments. ResourceSchedulerWrapper failed due to the

[jira] [Updated] (YARN-2361) remove duplicate entries (EXPIRE event) in the EnumSet of event type in RMAppAttempt state machine

[ https://issues.apache.org/jira/browse/YARN-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2361: Component/s: resourcemanager remove duplicate entries (EXPIRE event) in the EnumSet of event type in

[jira] [Created] (YARN-2361) remove duplicate entries (EXPIRE event) in the EnumSet of event type in RMAppAttempt state machine

zhihai xu created YARN-2361: --- Summary: remove duplicate entries (EXPIRE event) in the EnumSet of event type in RMAppAttempt state machine Key: YARN-2361 URL: https://issues.apache.org/jira/browse/YARN-2361

[jira] [Updated] (YARN-2361) remove duplicate entries (EXPIRE event) in the EnumSet of event type in RMAppAttempt state machine

[ https://issues.apache.org/jira/browse/YARN-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2361: Attachment: YARN-2361.000.patch remove duplicate entries (EXPIRE event) in the EnumSet of event type in

[jira] [Updated] (YARN-2354) DistributedShell may allocate more containers than client specified after it restarts

[ https://issues.apache.org/jira/browse/YARN-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2354: Attachment: YARN-2354-072514.patch The problem was on numRequestedContainers. In the previous version, initially,

[jira] [Commented] (YARN-2354) DistributedShell may allocate more containers than client specified after it restarts

[ https://issues.apache.org/jira/browse/YARN-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075165#comment-14075165 ] Jian He commented on YARN-2354: --- looks good. thanks for working on the patch Li !

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075166#comment-14075166 ] Karthik Kambatla commented on YARN-1726: +1 pending Jenkins.

[jira] [Commented] (YARN-2209) Replace allocate#resync command with ApplicationMasterNotRegisteredException to indicate AM to re-register on RM restart

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

[jira] [Commented] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

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

[jira] [Commented] (YARN-2212) ApplicationMaster needs to find a way to update the AMRMToken periodically

[ https://issues.apache.org/jira/browse/YARN-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075175#comment-14075175 ] Xuan Gong commented on YARN-2212: - Testcase failure is not related. ApplicationMaster

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

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

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper failed due to the AbstractYarnScheduler introduced in YARN-1041

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075187#comment-14075187 ] Karthik Kambatla commented on YARN-1726: Checking this in..

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper broken due to AbstractYarnScheduler

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1726: --- Summary: ResourceSchedulerWrapper broken due to AbstractYarnScheduler (was:

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper broken due to AbstractYarnScheduler

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

[jira] [Commented] (YARN-2361) remove duplicate entries (EXPIRE event) in the EnumSet of event type in RMAppAttempt state machine

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

[jira] [Updated] (YARN-1726) ResourceSchedulerWrapper broken due to AbstractYarnScheduler

[ https://issues.apache.org/jira/browse/YARN-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1726: -- Attachment: YARN-1726-7-branch2.patch update a patch for branch-2. ResourceSchedulerWrapper broken due to

[jira] [Updated] (YARN-1796) container-executor shouldn't require o-r permissions

[ https://issues.apache.org/jira/browse/YARN-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated YARN-1796: - Target Version/s: 2.6.0 (was: 2.4.0) container-executor shouldn't require o-r permissions

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper broken due to AbstractYarnScheduler

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

[jira] [Commented] (YARN-1796) container-executor shouldn't require o-r permissions

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

[jira] [Commented] (YARN-2069) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075220#comment-14075220 ] Wangda Tan commented on YARN-2069: -- Hi Mayank, Thanks for your detailed explanation, I

[jira] [Commented] (YARN-2354) DistributedShell may allocate more containers than client specified after it restarts

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

[jira] [Commented] (YARN-1796) container-executor shouldn't require o-r permissions

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

[jira] [Commented] (YARN-1726) ResourceSchedulerWrapper broken due to AbstractYarnScheduler

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

[jira] [Resolved] (YARN-2346) Add a 'status' command to yarn-daemon.sh

[ https://issues.apache.org/jira/browse/YARN-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2346. Resolution: Duplicate This is part of HADOOP-9902 now. Resolving. Add a 'status' command

[jira] [Assigned] (YARN-2346) Add a 'status' command to yarn-daemon.sh

[ https://issues.apache.org/jira/browse/YARN-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer reassigned YARN-2346: -- Assignee: Allen Wittenauer Add a 'status' command to yarn-daemon.sh

[jira] [Updated] (YARN-2346) Add a 'status' command to yarn-daemon.sh

[ https://issues.apache.org/jira/browse/YARN-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2346: --- Target Version/s: (was: 2.5.0) Add a 'status' command to yarn-daemon.sh

[jira] [Commented] (YARN-2247) Allow RM web services users to authenticate using delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075257#comment-14075257 ] Zhijie Shen commented on YARN-2247: --- +1 for the latest patch. [~vinodkv], do you have