[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043085#comment-14043085 ] Jian He commented on YARN-1366: --- btw, can you add necessary comments in the test body also,

[jira] [Created] (YARN-2210) resource manager fails to start if core-site.xml contains an xi:include

Sangjin Lee created YARN-2210: - Summary: resource manager fails to start if core-site.xml contains an xi:include Key: YARN-2210 URL: https://issues.apache.org/jira/browse/YARN-2210 Project: Hadoop YARN

[jira] [Commented] (YARN-2210) resource manager fails to start if core-site.xml contains an xi:include

[ https://issues.apache.org/jira/browse/YARN-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043099#comment-14043099 ] Sangjin Lee commented on YARN-2210: --- This is because core-site.xml is added in the

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043104#comment-14043104 ] Sunil G commented on YARN-2022: --- Thank You [~mayank_bansal] for the review. I understood the

[jira] [Commented] (YARN-2163) WebUI: Order of AppId in apps table should be consistent with ApplicationId.compareTo().

[ https://issues.apache.org/jira/browse/YARN-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043107#comment-14043107 ] Ravi Prakash commented on YARN-2163: This makes sense to me. I'll try to review and

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Thanks [~jianhe] for your comment, Uploaded a new patch rebased to latest

[jira] [Commented] (YARN-2163) WebUI: Order of AppId in apps table should be consistent with ApplicationId.compareTo().

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

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: application page.png Add preemption info to RM Web UI

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: (was: NM apps.png) Add preemption info to RM Web UI

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043143#comment-14043143 ] Wangda Tan commented on YARN-2022: -- I've revisited code, (1)

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2052.5.patch ContainerId creation after work preserving restart is broken

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Suppressed findbug warnings and fixed UT. Add preemption info to RM Web UI

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043238#comment-14043238 ] Wangda Tan commented on YARN-1039: -- bq. it must be set at application creation time and

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

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

[jira] [Commented] (YARN-2111) In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory but non-zero cores

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

[jira] [Commented] (YARN-2195) Clean a piece of code in ResourceRequest

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

[jira] [Commented] (YARN-2152) Recover missing container information

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

[jira] [Commented] (YARN-2072) RM/NM UIs and webservices are missing vcore information

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

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register of an app that was running before restart

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

[jira] [Commented] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

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

[jira] [Commented] (YARN-2109) Fix TestRM to work with both schedulers

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

[jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures

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

[jira] [Updated] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2201: Attachment: apache-yarn-2201.0.patch Hi [~rchiang], I wrote the code for that test. My apologies

[jira] [Updated] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2201: Attachment: apache-yarn-2201.1.patch Uploaded new patch with formatting fixed.

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: (was: YARN-2091.6.patch) ContainerId creation after work preserving restart is

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2052.6.patch ContainerId creation after work preserving restart is broken

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2091.6.patch Updated a patch to address comments by Jian and fixed a warning by

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Add preemption info to RM Web UI

Anyone knows which class is JobHistoryServer use to talk to a secured hdfs?

Hi all, I find JobHistoryServer have access to secured hdfs, can anyone paste some code or some class name it use for it to pass secure authentication? Thanks

[jira] [Commented] (YARN-2109) Fix TestRM to work with both schedulers

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043497#comment-14043497 ] Hudson commented on YARN-2109: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2072) RM/NM UIs and webservices are missing vcore information

[ https://issues.apache.org/jira/browse/YARN-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043504#comment-14043504 ] Hudson commented on YARN-2072: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2195) Clean a piece of code in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043490#comment-14043490 ] Hudson commented on YARN-2195: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043498#comment-14043498 ] Hudson commented on YARN-1365: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

[ https://issues.apache.org/jira/browse/YARN-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043492#comment-14043492 ] Hudson commented on YARN-2192: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2152) Recover missing container information

[ https://issues.apache.org/jira/browse/YARN-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043494#comment-14043494 ] Hudson commented on YARN-2152: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2111) In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043500#comment-14043500 ] Hudson commented on YARN-2111: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures

[ https://issues.apache.org/jira/browse/YARN-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043501#comment-14043501 ] Hudson commented on YARN-2074: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1785 (See

[jira] [Resolved] (YARN-2210) resource manager fails to start if core-site.xml contains an xi:include

[ https://issues.apache.org/jira/browse/YARN-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-2210. -- Resolution: Duplicate Resolving as a dup of YARN-1741, as that has more discussion around how this was

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Updated] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1741: - Priority: Critical (was: Minor) Bumping the priority of this based on YARN-2210 and the fact that

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

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

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

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

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043620#comment-14043620 ] Sangjin Lee commented on YARN-1741: --- +1 with the idea for the ConfigurationProvider to

[jira] [Updated] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2201: - Assignee: Varun Vasudev (was: Ray Chiang) TestRMWebServicesAppsModification dependent on

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043653#comment-14043653 ] Ray Chiang commented on YARN-2201: -- [~vvasudev], since you already uploaded a patch, I've

[jira] [Commented] (YARN-2111) In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory but non-zero cores

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

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register of an app that was running before restart

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

[jira] [Commented] (YARN-2072) RM/NM UIs and webservices are missing vcore information

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

[jira] [Commented] (YARN-2192) TestRMHA fails when run with a mix of Schedulers

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

[jira] [Commented] (YARN-2152) Recover missing container information

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

[jira] [Commented] (YARN-2109) Fix TestRM to work with both schedulers

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

[jira] [Commented] (YARN-2074) Preemption of AM containers shouldn't count towards AM failures

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

[jira] [Commented] (YARN-2195) Clean a piece of code in ResourceRequest

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

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043758#comment-14043758 ] Gera Shegalov commented on YARN-1741: - Since there is a general problem of loading conf

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

Xuan Gong created YARN-2211: --- Summary: RMStateStore needs to save AMRMToken master key for recovery when RM restart/failover happens Key: YARN-2211 URL: https://issues.apache.org/jira/browse/YARN-2211

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

Xuan Gong created YARN-2212: --- Summary: ApplicationMaster needs to find a way to update the AMRMToken periodically Key: YARN-2212 URL: https://issues.apache.org/jira/browse/YARN-2212 Project: Hadoop YARN

[jira] [Created] (YARN-2213) Change proxy-user cookie log in AmIpFilter to DEBUG

Ted Yu created YARN-2213: Summary: Change proxy-user cookie log in AmIpFilter to DEBUG Key: YARN-2213 URL: https://issues.apache.org/jira/browse/YARN-2213 Project: Hadoop YARN Issue Type: Task

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043855#comment-14043855 ] Ray Chiang commented on YARN-2201: -- [~vvasudev]. Thanks, I see how your change works.

[jira] [Updated] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1741: -- Target Version/s: 2.5.0 Targetting for 2.5. [~sirianni]/[~jeffgx619], can one

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Updated] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2204: --- Priority: Trivial (was: Major) TestAMRestart#testAMRestartWithExistingContainers assumes

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043912#comment-14043912 ] Vinod Kumar Vavilapalli commented on YARN-2204: --- Not sure why this test

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043922#comment-14043922 ] Karthik Kambatla commented on YARN-2204: Sorry Vinod. Didn't see your comments.

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043938#comment-14043938 ] Eric Sirianni commented on YARN-1741: - [~vinodkv], unfortunately I'm no longer working

[jira] [Commented] (YARN-1727) provide (async) application lifecycle events to management tools

[ https://issues.apache.org/jira/browse/YARN-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044003#comment-14044003 ] Steve Loughran commented on YARN-1727: -- Yes, this can and should be appilcation

[jira] [Reopened] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-2204: --- Cool, reopening it for the right fix..

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044059#comment-14044059 ] Jian He commented on YARN-2052: --- - we can update the structure graph in ZKRMStateStore to

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

Ashwin Shankar created YARN-2214: Summary: preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness Key: YARN-2214 URL: https://issues.apache.org/jira/browse/YARN-2214 Project:

[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=14044066#comment-14044066 ] Sandy Ryza commented on YARN-2214: -- Makes sense preemptContainerPreCheck() in

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

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar reassigned YARN-2214: Assignee: Ashwin Shankar preemptContainerPreCheck() in FSParentQueue delays convergence

[jira] [Assigned] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-1741: - Assignee: Xuan Gong Tx for the note, Eric. Assigning this to Xuan for now

[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=14044096#comment-14044096 ] Vinod Kumar Vavilapalli commented on YARN-2209: --- Makes sense. We need to be

[jira] [Commented] (YARN-2171) AMs block on the CapacityScheduler lock during allocate()

[ https://issues.apache.org/jira/browse/YARN-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044100#comment-14044100 ] Vinod Kumar Vavilapalli commented on YARN-2171: --- +1, looks good. Checking

[jira] [Commented] (YARN-2171) AMs block on the CapacityScheduler lock during allocate()

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

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044118#comment-14044118 ] Jian He commented on YARN-614: -- Xuan, can you emulate what are the failures that should not be

[jira] [Commented] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

[ https://issues.apache.org/jira/browse/YARN-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044153#comment-14044153 ] Xuan Gong commented on YARN-2208: - This patch only focused on the changes on

[jira] [Updated] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

[ https://issues.apache.org/jira/browse/YARN-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-2208: Attachment: YARN-2208.1.patch AMRMTokenManager need to have a way to roll over AMRMToken

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-614: --- Summary: Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-614: --- Summary: Separate AM failures from hardware failure or YARN error and do not count them to (was: Retry

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044184#comment-14044184 ] Xuan Gong commented on YARN-614: Ignore three type of failure with the following

[jira] [Commented] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

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

[jira] [Commented] (YARN-2208) AMRMTokenManager need to have a way to roll over AMRMToken

[ https://issues.apache.org/jira/browse/YARN-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044199#comment-14044199 ] Xuan Gong commented on YARN-2208: - The test case failure in TestRMRestart is expected. We

[jira] [Updated] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2204: Attachment: YARN-2204_addendum.patch Makes sense. I've attached an addendum patch that's scheduler

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044215#comment-14044215 ] Jian He commented on YARN-2181: --- - how about the parent queue metrics, are we capturing

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044217#comment-14044217 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] If we dont use getAbsoluteCapacity

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044218#comment-14044218 ] Mayank Bansal commented on YARN-2181: - If we are adding this information into Web UI

[jira] [Updated] (YARN-1710) Admission Control: agents to allocate reservation

[ https://issues.apache.org/jira/browse/YARN-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-1710: --- Attachment: YARN-1710.patch Admission Control: agents to allocate reservation

[jira] [Assigned] (YARN-1710) Admission Control: agents to allocate reservation

[ https://issues.apache.org/jira/browse/YARN-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino reassigned YARN-1710: -- Assignee: Carlo Curino (was: Subramaniam Venkatraman Krishnan) Admission Control: agents to

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-1710) Admission Control: agents to allocate reservation

[ https://issues.apache.org/jira/browse/YARN-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044243#comment-14044243 ] Carlo Curino commented on YARN-1710: I uploaded a patch that contains a

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044270#comment-14044270 ] Wangda Tan commented on YARN-2022: -- Hi [~mayank_bansal], For existing CapacityScheduler

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Add preemption info to RM Web UI

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044280#comment-14044280 ] Wangda Tan commented on YARN-2181: -- [~jianhe], thanks for all your comments, bq. how about

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044281#comment-14044281 ] Wangda Tan commented on YARN-2181: -- Hi [~mayank_bansal], {quote} If we are adding this

[jira] [Commented] (YARN-1710) Admission Control: agents to allocate reservation

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

  1   2   >