[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

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

[jira] [Commented] (YARN-1714) Per user and per queue view in YARN RM

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

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good back again

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

[jira] [Commented] (YARN-2527) NPE in ApplicationACLsManager

[ https://issues.apache.org/jira/browse/YARN-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155744#comment-14155744 ] Zhijie Shen commented on YARN-2527: --- Thanks for be patient about the comment. How about

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good back again

[ https://issues.apache.org/jira/browse/YARN-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155747#comment-14155747 ] Varun Vasudev commented on YARN-90: --- The release audit warning is unrelated to the patch.

[jira] [Updated] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-1198: -- Attachment: YARN-1198.10.patch And again, this time, with the additional files, .10 (nee .9, .7)

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

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

[jira] [Updated] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1391: -- Attachment: YARN-1391.v2.patch Lost node list should be identify by NodeId

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155767#comment-14155767 ] Craig Welch commented on YARN-1198: --- The Jenkins failures do not actually seem to have

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155764#comment-14155764 ] Craig Welch commented on YARN-1198: --- [~john.jian.fang] I look a look at implementing the

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

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

[jira] [Updated] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Attachment: YARN-2624.001.patch Attaching a patch that cleans up the local resource cache

[jira] [Commented] (YARN-2628) Capacity scheduler with DominantResourceCalculator carries out reservation even though slots are free

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

[jira] [Commented] (YARN-2591) AHSWebServices should return FORBIDDEN(403) if the request user doesn't have access to the history data

[ https://issues.apache.org/jira/browse/YARN-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155810#comment-14155810 ] Jian He commented on YARN-2591: --- looked at the patch, maybe create a new exception type,

[jira] [Commented] (YARN-2613) NMClient doesn't have retries for supporting rolling-upgrades

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

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

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

[jira] [Updated] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

[ https://issues.apache.org/jira/browse/YARN-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2617: -- Attachment: YARN-2617.5.patch Upload same patch, not sure why jenkins report eclipse failure NM does not need

[jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId

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

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155828#comment-14155828 ] Jian He commented on YARN-2562: --- bq. A number at the end for me always pointed to the

[jira] [Updated] (YARN-2635) TestRMRestart fails with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2635: -- Attachment: YARN-2635-1.patch Post a patch which let TestRMRestart run with all types of schedulers, and fix

[jira] [Commented] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches

[ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155840#comment-14155840 ] Vinod Kumar Vavilapalli commented on YARN-443: -- The new test

[jira] [Commented] (YARN-1972) Implement secure Windows Container Executor

[ https://issues.apache.org/jira/browse/YARN-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155842#comment-14155842 ] Vinod Kumar Vavilapalli commented on YARN-1972: --- BTW, the new test

[jira] [Updated] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2624: Attachment: YARN-2624.001.patch No apparent failure in jenkins output. Uploading it again Resource

[jira] [Created] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

Wei Yan created YARN-2638: - Summary: Let TestRM run with all types of schedulers (FIFO, Capacity, Fair) Key: YARN-2638 URL: https://issues.apache.org/jira/browse/YARN-2638 Project: Hadoop YARN

[jira] [Updated] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

[ https://issues.apache.org/jira/browse/YARN-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2638: -- Description: TestRM fails when using FairScheduler. The failures not shown in trunk as the trunk uses the

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155868#comment-14155868 ] Tsuyoshi OZAWA commented on YARN-2562: -- My concern at first was that AppMaster won't

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

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

[jira] [Commented] (YARN-2635) TestRMRestart fails with FairScheduler

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

[jira] [Commented] (YARN-2446) Using TimelineNamespace to shield the entities of a user

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

[jira] [Updated] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2562: - Attachment: YARN-2562.3.patch ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[jira] [Updated] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

[ https://issues.apache.org/jira/browse/YARN-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2638: -- Description: TestRM fails when using FairScheduler or FifoScheduler. The failures not shown in trunk as the

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

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

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

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

[jira] [Updated] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

[ https://issues.apache.org/jira/browse/YARN-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2617: -- Attachment: YARN-2617.5.patch same patch uploaded again NM does not need to send finished container whose APP

[jira] [Commented] (YARN-2446) Using TimelineNamespace to shield the entities of a user

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

[jira] [Created] (YARN-2639) TestClientToAMTokens should run with all types of schedulers

Wei Yan created YARN-2639: - Summary: TestClientToAMTokens should run with all types of schedulers Key: YARN-2639 URL: https://issues.apache.org/jira/browse/YARN-2639 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2446) Using TimelineNamespace to shield the entities of a user

[ https://issues.apache.org/jira/browse/YARN-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155930#comment-14155930 ] Vinod Kumar Vavilapalli commented on YARN-2446: --- Merged this into branch-2.6

[jira] [Updated] (YARN-2639) TestClientToAMTokens should run with all types of schedulers

[ https://issues.apache.org/jira/browse/YARN-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2639: -- Attachment: YARN-2639-1.patch TestClientToAMTokens should run with all types of schedulers

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

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

[jira] [Commented] (YARN-2639) TestClientToAMTokens should run with all types of schedulers

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

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

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

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155949#comment-14155949 ] Tsuyoshi OZAWA commented on YARN-2562: -- [~jianhe], [~vinodkv], could you check the

[jira] [Commented] (YARN-2628) Capacity scheduler with DominantResourceCalculator carries out reservation even though slots are free

[ https://issues.apache.org/jira/browse/YARN-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155954#comment-14155954 ] Jian He commented on YARN-2628: --- looks good, +1 Capacity scheduler with

[jira] [Updated] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

[ https://issues.apache.org/jira/browse/YARN-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2617: -- Attachment: YARN-2617.6.patch NM does not need to send finished container whose APP is not running to RM

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

[ https://issues.apache.org/jira/browse/YARN-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155960#comment-14155960 ] Jun Gong commented on YARN-2617: It seems that there is something wrong with Jenkins.

[jira] [Updated] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

[ https://issues.apache.org/jira/browse/YARN-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2638: -- Attachment: YARN-2638-1.patch Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

[jira] [Commented] (YARN-2617) NM does not need to send finished container whose APP is not running to RM

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

[jira] [Commented] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

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

[jira] [Commented] (YARN-1414) with Fair Scheduler reserved MB in WebUI is leaking when killing waiting jobs

[ https://issues.apache.org/jira/browse/YARN-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156020#comment-14156020 ] Sandy Ryza commented on YARN-1414: -- [~jrottinghuis] I will take a look. [~l201514] mind

[jira] [Updated] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2562: - Attachment: YARN-2562.4.patch [~jianhe], good catch. Fixed the comment. ContainerId@toString()

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

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

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156073#comment-14156073 ] Anubhav Dhoot commented on YARN-2624: - Failure seems unrelated to changes and does not

[jira] [Commented] (YARN-2624) Resource Localization fails on a cluster due to existing cache directories

[ https://issues.apache.org/jira/browse/YARN-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156079#comment-14156079 ] Anubhav Dhoot commented on YARN-2624: - The fix addresses the scenario moving from pre

[jira] [Updated] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

[ https://issues.apache.org/jira/browse/YARN-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2562: - Attachment: YARN-2562.5.patch Rebased on trunk. ContainerId@toString() is unreadable for epoch 0

[jira] [Commented] (YARN-2562) ContainerId@toString() is unreadable for epoch 0 after YARN-2182

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

[jira] [Commented] (YARN-2254) TestRMWebServicesAppsModification should run against both CS and FS

[ https://issues.apache.org/jira/browse/YARN-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156104#comment-14156104 ] zhihai xu commented on YARN-2254: - The release audit warning is not related to my change.

<    1   2