[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=14046817#comment-14046817 ] Hudson commented on YARN-2201: -- FAILURE: Integrated in Hadoop-Yarn-trunk #597 (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=14046819#comment-14046819 ] Hudson commented on YARN-2204: -- FAILURE: Integrated in Hadoop-Yarn-trunk #597 (See

[jira] [Commented] (YARN-2104) Scheduler queue filter failed to work because index of queue column changed

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

[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=14046826#comment-14046826 ] Rohith commented on YARN-1366: -- Looking into fix findbug warning and test case. Will update

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14046853#comment-14046853 ] Remus Rusanu commented on YARN-2198: I got this working using LPC, but there are some

[jira] [Commented] (YARN-2104) Scheduler queue filter failed to work because index of queue column changed

[ https://issues.apache.org/jira/browse/YARN-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14046867#comment-14046867 ] Hudson commented on YARN-2104: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1788 (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=14046871#comment-14046871 ] Hudson commented on YARN-2204: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1788 (See

[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=14046869#comment-14046869 ] Hudson commented on YARN-2201: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1788 (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=14046883#comment-14046883 ] Hudson commented on YARN-2204: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1815 (See

[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=14046882#comment-14046882 ] Hudson commented on YARN-2201: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1815 (See

[jira] [Commented] (YARN-2104) Scheduler queue filter failed to work because index of queue column changed

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

[jira] [Updated] (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:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.6.patch Attached updated the patch. Please review the patch AM should implement Resync

[jira] [Updated] (YARN-2223) NPE on ResourceManager recover

[ https://issues.apache.org/jira/browse/YARN-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2223: - Environment: JDK 8u5 NPE on ResourceManager recover --

[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=14046900#comment-14046900 ] Hadoop QA commented on YARN-1366: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

[ https://issues.apache.org/jira/browse/YARN-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kawa updated YARN-2230: Summary: Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code) (was:

[jira] [Created] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code to show)

Adam Kawa created YARN-2230: --- Summary: Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code to show) Key: YARN-2230 URL: https://issues.apache.org/jira/browse/YARN-2230

[jira] [Updated] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

[ https://issues.apache.org/jira/browse/YARN-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kawa updated YARN-2230: Affects Version/s: 2.4.0 Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml

[jira] [Updated] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

[ https://issues.apache.org/jira/browse/YARN-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kawa updated YARN-2230: Description: When a user requests more vcores than the allocation limit (e.g. mapreduce.map.cpu.vcores is

[jira] [Updated] (YARN-2230) Fix description of yarn.scheduler.maximum-allocation-vcores in yarn-default.xml (or code)

[ https://issues.apache.org/jira/browse/YARN-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kawa updated YARN-2230: Component/s: scheduler client Fix description of yarn.scheduler.maximum-allocation-vcores

[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=14047000#comment-14047000 ] Jian He commented on YARN-2052: --- found that may be we can change epochProto to use int64

[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=14047002#comment-14047002 ] Jian He commented on YARN-614: -- Committed to trunk and branch-2, thanks Xuan! Separate AM

[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=14047006#comment-14047006 ] Hudson commented on YARN-614: - SUCCESS: Integrated in Hadoop-trunk-Commit #5797 (See

[jira] [Commented] (YARN-2223) NPE on ResourceManager recover

[ https://issues.apache.org/jira/browse/YARN-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047017#comment-14047017 ] Jian He commented on YARN-2223: --- looks like the some attempt data is missing . Can you find

[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.12.patch Sounds good. Updated a patch: * Made EpochProto#epoch int64. *

[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=14047020#comment-14047020 ] Jian He commented on YARN-2052: --- looks good, pending jenkins. ContainerId creation after

[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=14047026#comment-14047026 ] Hadoop QA commented on YARN-2052: - {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=14047031#comment-14047031 ] Tsuyoshi OZAWA commented on YARN-2052: -- Thank you for the review, Jian. The test