[jira] [Updated] (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:all-tabpanel ] Sunil G updated YARN-2022: -- Attachment: YARN-2022.3.patch Updating patch to correct test failures. Preempting an Application Master

[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: apache-yarn-1702.12.patch Uploaded new patch addressing comments. {quote} AppInfo.java

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

[jira] [Updated] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-1885: - Attachment: YARN-1885.patch YARN-1885.patch Uploaded new patch against trunk. [~jianhe],

[jira] [Commented] (YARN-1702) Expose kill app functionality as part of RM web services

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

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

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

[jira] [Commented] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

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

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should return the DummyApplicationResourceUsageReport for all invalid accesses

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

[jira] [Commented] (YARN-2073) Fair Scheduler: Add a utilization threshold to prevent preempting resources when cluster is free

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027644#comment-14027644 ] Andrey Stepachev commented on YARN-2073: I read code and don't cleanly understand

[jira] [Created] (YARN-2145) FairScheduler can assign more resources to queue with MaxShare set.

Andrey Stepachev created YARN-2145: -- Summary: FairScheduler can assign more resources to queue with MaxShare set. Key: YARN-2145 URL: https://issues.apache.org/jira/browse/YARN-2145 Project: Hadoop

[jira] [Updated] (YARN-2145) FairScheduler can assign more resources to queue with MaxShare set.

[ https://issues.apache.org/jira/browse/YARN-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2145: --- Description: method fair.FSQueue#assignContainerPreCheck() uses Resources.fitsIn

[jira] [Commented] (YARN-2145) FairScheduler can assign more resources to queue with MaxShare set.

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

[jira] [Created] (YARN-2146) Yarn logs report error when redirecting logs output to a file

Chen He created YARN-2146: - Summary: Yarn logs report error when redirecting logs output to a file Key: YARN-2146 URL: https://issues.apache.org/jira/browse/YARN-2146 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

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

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should return the DummyApplicationResourceUsageReport for all invalid accesses

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

[jira] [Commented] (YARN-2145) FairScheduler can assign more resources to queue with MaxShare set.

[ https://issues.apache.org/jira/browse/YARN-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027813#comment-14027813 ] Wei Yan commented on YARN-2145: --- duplicate with YARN-2083? FairScheduler can assign more

[jira] [Commented] (YARN-2145) FairScheduler can assign more resources to queue with MaxShare set.

[ https://issues.apache.org/jira/browse/YARN-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027815#comment-14027815 ] Andrey Stepachev commented on YARN-2145: yes, exactly the same problem.

[jira] [Resolved] (YARN-2146) Yarn logs report error when redirecting logs output to a file

[ https://issues.apache.org/jira/browse/YARN-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He resolved YARN-2146. --- Resolution: Not a Problem Yarn logs report error when redirecting logs output to a file

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027820#comment-14027820 ] Steve Loughran commented on YARN-2139: -- well, I am happy to be wrong here. I was of

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should return the DummyApplicationResourceUsageReport for all invalid accesses

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

[jira] [Commented] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

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

[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=14027938#comment-14027938 ] Jonathan Eagles commented on YARN-1198: --- Since headroom calculation is used reducer

[jira] [Updated] (YARN-1857) CapacityScheduler headroom doesn't account for other AM's running

[ https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-1857: -- Priority: Critical (was: Major) CapacityScheduler headroom doesn't account for other AM's

[jira] [Updated] (YARN-1857) CapacityScheduler headroom doesn't account for other AM's running

[ https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-1857: -- Target Version/s: 2.4.1 (was: 2.4.0) CapacityScheduler headroom doesn't account for other

[jira] [Commented] (YARN-1857) CapacityScheduler headroom doesn't account for other AM's running

[ https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027943#comment-14027943 ] Jonathan Eagles commented on YARN-1857: --- Bumping the priority since reducer

[jira] [Updated] (YARN-2146) Yarn logs aggregation error

[ https://issues.apache.org/jira/browse/YARN-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2146: -- Summary: Yarn logs aggregation error (was: Yarn logs report error when redirecting logs output to a file)

[jira] [Created] (YARN-2147) client lacks delegation token exception details when application submit fails

Jason Lowe created YARN-2147: Summary: client lacks delegation token exception details when application submit fails Key: YARN-2147 URL: https://issues.apache.org/jira/browse/YARN-2147 Project: Hadoop

[jira] [Commented] (YARN-2147) client lacks delegation token exception details when application submit fails

[ https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027979#comment-14027979 ] Jason Lowe commented on YARN-2147: -- For example, here's a sample log from a client

[jira] [Created] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

Wangda Tan created YARN-2148: Summary: TestNMClient failed due more exit code values added and passed to AM Key: YARN-2148 URL: https://issues.apache.org/jira/browse/YARN-2148 Project: Hadoop YARN

[jira] [Commented] (YARN-2149) Test failed in TestRMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028022#comment-14028022 ] Tsuyoshi OZAWA commented on YARN-2149: -- Thank you for reporting, [~wangda]. This

[jira] [Updated] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2148: - Attachment: YARN-2148.patch Attached a patch for this. TestNMClient failed due more exit code values

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028016#comment-14028016 ] Wangda Tan commented on YARN-1885: -- I've looked into failed tests, 1) TestNMClient, this

[jira] [Created] (YARN-2149) Test failed in TestRMAdminCLI

Wangda Tan created YARN-2149: Summary: Test failed in TestRMAdminCLI Key: YARN-2149 URL: https://issues.apache.org/jira/browse/YARN-2149 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2149) Test failed in TestRMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028026#comment-14028026 ] Wangda Tan commented on YARN-2149: -- [~ozawa], thanks for pointing this, I'll close this

[jira] [Assigned] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-2148: Assignee: Wangda Tan TestNMClient failed due more exit code values added and passed to AM

[jira] [Resolved] (YARN-2149) Test failed in TestRMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-2149. -- Resolution: Duplicate Assignee: Wangda Tan Test failed in TestRMAdminCLI

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028030#comment-14028030 ] Wangda Tan commented on YARN-1885: -- Update: YARN-2149 is a duplicated JIRA of YARN-2075,

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028034#comment-14028034 ] Tsuyoshi OZAWA commented on YARN-2148: -- [~leftnoteasy], thank you for taking this

[jira] [Commented] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

[ https://issues.apache.org/jira/browse/YARN-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028075#comment-14028075 ] Jian He commented on YARN-2125: --- Looks good, +1. Committing this

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

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

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

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

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister 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=14028139#comment-14028139 ] Tsuyoshi OZAWA commented on YARN-1365: -- [~jianhe], [~adhoot], yes, +1 for keeping the

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028142#comment-14028142 ] Tsuyoshi OZAWA commented on YARN-2148: -- The test failure is not related to this JIRA.

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028162#comment-14028162 ] Tsuyoshi OZAWA commented on YARN-1885: -- Done. Thanks you for reporting, Wangda. RM

[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=14028174#comment-14028174 ] Mayank Bansal commented on YARN-2022: - hi [~sunilg] Thanks for the patch. There is

[jira] [Commented] (YARN-1911) NullPointerException in ResourceOption.getOverCommitTimeout()

[ https://issues.apache.org/jira/browse/YARN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028175#comment-14028175 ] Tsuyoshi OZAWA commented on YARN-1911: -- Thank you for taking this JIRA, [~kj-ki]. IMO,

[jira] [Commented] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

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

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028216#comment-14028216 ] Bikas Saha commented on YARN-2148: -- [~ozawa] Can you please apply this patch and run the

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028213#comment-14028213 ] Bikas Saha commented on YARN-2148: -- lgtm. +1. TestNMClient failed due more exit code

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028238#comment-14028238 ] Tsuyoshi OZAWA commented on YARN-2148: -- Good point. ok, I'll report the result of the

[jira] [Commented] (YARN-2073) Fair Scheduler: Add a utilization threshold to prevent preempting resources when cluster is free

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028256#comment-14028256 ] Wei Yan commented on YARN-2073: --- should be a mistake here. need to use allocated resource.

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028321#comment-14028321 ] Vinod Kumar Vavilapalli commented on YARN-1885: --- YARN-920 sounds related..

[jira] [Updated] (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:all-tabpanel ] Sunil G updated YARN-2022: -- Attachment: YARN-2022.4.patch Thank you [~mayank_bansal] for the review. I updated a patch as per the review

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028392#comment-14028392 ] Nathan Roberts commented on YARN-2056: -- Could this be accomplished by changing

[jira] [Created] (YARN-2151) FairScheduler option for global preemption within hierarchical queues

Andrey Stepachev created YARN-2151: -- Summary: FairScheduler option for global preemption within hierarchical queues Key: YARN-2151 URL: https://issues.apache.org/jira/browse/YARN-2151 Project:

[jira] [Updated] (YARN-2151) FairScheduler option for global preemption within hierarchical queues

[ https://issues.apache.org/jira/browse/YARN-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2151: --- Attachment: YARN-2151.patch FairScheduler option for global preemption within hierarchical

[jira] [Updated] (YARN-2151) FairScheduler option for global preemption within hierarchical queues

[ https://issues.apache.org/jira/browse/YARN-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2151: --- Description: FairScheduler has hierarchical queues, but fair share calculation and

[jira] [Updated] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-1769: Attachment: YARN-1769.patch patch to fix TestReservations after YARN-1474 CapacityScheduler:

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028427#comment-14028427 ] Hadoop QA commented on YARN-1769: - {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=14028448#comment-14028448 ] Hadoop QA commented on YARN-2022: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028461#comment-14028461 ] Tsuyoshi OZAWA commented on YARN-2148: -- [~bikassaha], I confirmed there are no test

[jira] [Commented] (YARN-2151) FairScheduler option for global preemption within hierarchical queues

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

[jira] [Updated] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

[ https://issues.apache.org/jira/browse/YARN-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1919: - Attachment: YARN-1919.1.patch I faced the problem and looked at the cause of the

[jira] [Commented] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

[ https://issues.apache.org/jira/browse/YARN-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028520#comment-14028520 ] Tsuyoshi OZAWA commented on YARN-1919: -- One additional point: the change against

[jira] [Updated] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

[ https://issues.apache.org/jira/browse/YARN-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1919: - Attachment: YARN-1919.1.patch Log yarn.resourcemanager.cluster-id is required for HA instead of

[jira] [Updated] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

[ https://issues.apache.org/jira/browse/YARN-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1919: - Attachment: (was: YARN-1919.1.patch) Log yarn.resourcemanager.cluster-id is required for HA

[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: apache-yarn-1702.13.patch {quote} We now have double Audit logs in some cases

[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=14028572#comment-14028572 ] Vinod Kumar Vavilapalli commented on YARN-2022: --- bq. Me and Vinod Kumar

[jira] [Assigned] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

[ https://issues.apache.org/jira/browse/YARN-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1919: -- Assignee: Tsuyoshi OZAWA (was: Karthik Kambatla) Log yarn.resourcemanager.cluster-id

[jira] [Commented] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028607#comment-14028607 ] Xuan Gong commented on YARN-1779: - Increase the priority. I think this is a serious issue,

[jira] [Updated] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1779: Priority: Blocker (was: Critical) Handle AMRMTokens across RM failover

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

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

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028619#comment-14028619 ] Tsuyoshi OZAWA commented on YARN-2148: -- Thanks for the quick fix, Wangda, and thanks

[jira] [Commented] (YARN-1702) Expose kill app functionality as part of RM web services

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

[jira] [Commented] (YARN-1900) yarn.log.server.url needs to specify an http:// prefix

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

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028639#comment-14028639 ] Zhijie Shen commented on YARN-2148: --- {code} - new Integer[] {137, 143,

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028643#comment-14028643 ] Wangda Tan commented on YARN-2148: -- Thanks for [~ozawa] and [~bikassaha] review and

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028644#comment-14028644 ] Wangda Tan commented on YARN-2124: -- Thanks [~jianhe] for reviewing and committing this!

[jira] [Commented] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

[ https://issues.apache.org/jira/browse/YARN-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028645#comment-14028645 ] Wangda Tan commented on YARN-2125: -- Thanks [~jianhe] for reviewing and committing this!

[jira] [Commented] (YARN-1919) Log yarn.resourcemanager.cluster-id is required for HA instead of throwing NPE

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

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028662#comment-14028662 ] Wangda Tan commented on YARN-2148: -- Sorry [~zjshen], I missed your comment, bq.

[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=14028667#comment-14028667 ] Wangda Tan commented on YARN-2022: -- Thanks for this summary, [~vinodkv] As you mentioned,

[jira] [Commented] (YARN-2150) Add CLI to list applications by final-status

[ https://issues.apache.org/jira/browse/YARN-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028692#comment-14028692 ] Zhijie Shen commented on YARN-2150: --- YARN-1480 is going to cover the final-status option.

[jira] [Resolved] (YARN-2150) Add CLI to list applications by final-status

[ https://issues.apache.org/jira/browse/YARN-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya resolved YARN-2150. --- Resolution: Duplicate Closed as duplicate of YARN-1480. Thanks for pointing this out.

[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=14028707#comment-14028707 ] Jian He commented on YARN-2052: --- bq. The monotonically increasing sequence could be 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=14028713#comment-14028713 ] Carlo Curino commented on YARN-2022: [~vinodkv] I agree with your/Mayank take on it. We

[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=14028717#comment-14028717 ] Tsuyoshi OZAWA commented on YARN-2052: -- s/epoch number is/epoch number should be/

[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=14028716#comment-14028716 ] Tsuyoshi OZAWA commented on YARN-2052: -- {quote} we probably need to persist the epoch

[jira] [Updated] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI list command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1480: -- Target Version/s: 2.5.0 Hadoop Flags: (was: Reviewed) RM web services getApps() accepts many

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI list command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028724#comment-14028724 ] Hadoop QA commented on YARN-1480: - {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=14028728#comment-14028728 ] Jian He commented on YARN-2052: --- On RM startup, RM may need to read and rewrite this epoch

[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=14028734#comment-14028734 ] Bikas Saha commented on YARN-2052: -- Dont we already read and write synchronously from the

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

Jian He created YARN-2152: - Summary: Recover missing container information Key: YARN-2152 URL: https://issues.apache.org/jira/browse/YARN-2152 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-2153) Ensure distributed shell work with RM work-preserving recovery

Jian He created YARN-2153: - Summary: Ensure distributed shell work with RM work-preserving recovery Key: YARN-2153 URL: https://issues.apache.org/jira/browse/YARN-2153 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Target Version/s: 2.4.1 (was: 2.5.0) In fair scheduler, Queue should not been assigned more containers when

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

[ https://issues.apache.org/jira/browse/YARN-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2152: -- Description: Container information such as container priority and container start time cannot be recovered

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028741#comment-14028741 ] Yi Tian commented on YARN-2083: --- Thanks [~ywskycn] [~kasha], Here is the final patch file.

[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=14028744#comment-14028744 ] Jian He commented on YARN-2052: --- bq. Dont we already read and write synchronously from the

[jira] [Commented] (YARN-2148) TestNMClient failed due more exit code values added and passed to AM

[ https://issues.apache.org/jira/browse/YARN-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028747#comment-14028747 ] Zhijie Shen commented on YARN-2148: --- bq. This should be a rare case, but it should be

[jira] [Commented] (YARN-1885) RM may not send the finished signal to some nodes where the application ran after RM restarts

[ https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028752#comment-14028752 ] Wangda Tan commented on YARN-1885: -- [~vinodkv], Yes, it should be a related issue. RM

  1   2   >