[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746967#comment-14746967 ] Jian He commented on YARN-4000: --- I see, a few more comments: - QueueException -> QueueInvalidException - If

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746978#comment-14746978 ] Hadoop QA commented on YARN-4135: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746979#comment-14746979 ] Hadoop QA commented on YARN-4034: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746989#comment-14746989 ] Rohith Sharma K S commented on YARN-4034: - Patch need to be rebased. I will upload rebased patch..

[jira] [Created] (YARN-4165) An outstanding container request makes all nodes to be reserved causing all jobs pending

Weiwei Yang created YARN-4165: - Summary: An outstanding container request makes all nodes to be reserved causing all jobs pending Key: YARN-4165 URL: https://issues.apache.org/jira/browse/YARN-4165

[jira] [Assigned] (YARN-4165) An outstanding container request makes all nodes to be reserved causing all jobs pending

[ https://issues.apache.org/jira/browse/YARN-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang reassigned YARN-4165: - Assignee: Weiwei Yang > An outstanding container request makes all nodes to be reserved causing

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746972#comment-14746972 ] Hadoop QA commented on YARN-4141: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Created] (YARN-4166) Support changing container cpu resource

Jian He created YARN-4166: - Summary: Support changing container cpu resource Key: YARN-4166 URL: https://issues.apache.org/jira/browse/YARN-4166 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-4164) Retrospect update ApplicationPriority API return type

[ https://issues.apache.org/jira/browse/YARN-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746952#comment-14746952 ] Sunil G commented on YARN-4164: --- Hi [~rohithsharma] Thanks for raising this. To an extent I also feel that

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746985#comment-14746985 ] Varun Saxena commented on YARN-4000: [~jianhe], moreover there will be subclasses of RMAppEvent which

[jira] [Updated] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4034: Attachment: 0002-YARN-4034.patch Updated rebased patch!! > Render cluster Max Priority in

[jira] [Updated] (YARN-4152) NM crash with NPE when LogAggregationService#stopContainer called for absent container

[ https://issues.apache.org/jira/browse/YARN-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4152: --- Summary: NM crash with NPE when LogAggregationService#stopContainer called for absent

[jira] [Commented] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747149#comment-14747149 ] Hadoop QA commented on YARN-4034: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747225#comment-14747225 ] Hadoop QA commented on YARN-4034: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-4166) Support changing container cpu resource

[ https://issues.apache.org/jira/browse/YARN-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747021#comment-14747021 ] Jian He commented on YARN-4166: --- yes, that's the idea. > Support changing container cpu resource >

[jira] [Assigned] (YARN-4166) Support changing container cpu resource

[ https://issues.apache.org/jira/browse/YARN-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-4166: --- Assignee: Naganarasimha G R > Support changing container cpu resource >

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747179#comment-14747179 ] Hudson commented on YARN-4078: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #402 (See

[jira] [Created] (YARN-4167) NPE on RMActiveServices#serviceStop when store is null

Bibin A Chundatt created YARN-4167: -- Summary: NPE on RMActiveServices#serviceStop when store is null Key: YARN-4167 URL: https://issues.apache.org/jira/browse/YARN-4167 Project: Hadoop YARN

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

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

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746999#comment-14746999 ] Jian He commented on YARN-4000: --- sounds good to me. thanks > RM crashes with NPE if leaf queue becomes

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746997#comment-14746997 ] Jian He commented on YARN-4000: --- sounds good to me. thanks > RM crashes with NPE if leaf queue becomes

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14746998#comment-14746998 ] Jian He commented on YARN-4000: --- sounds good to me. thanks > RM crashes with NPE if leaf queue becomes

[jira] [Issue Comment Deleted] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4000: -- Comment: was deleted (was: sounds good to me. thanks) > RM crashes with NPE if leaf queue becomes parent queue

[jira] [Issue Comment Deleted] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4000: -- Comment: was deleted (was: sounds good to me. thanks) > RM crashes with NPE if leaf queue becomes parent queue

[jira] [Commented] (YARN-4166) Support changing container cpu resource

[ https://issues.apache.org/jira/browse/YARN-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747001#comment-14747001 ] Naganarasimha G R commented on YARN-4166: - Hi [~jianhe ], IIUC cgroups controls the CPU usage so is

[jira] [Updated] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4034: Attachment: 0003-YARN-4034.patch Updated the patch fixing test case failures > Render

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747106#comment-14747106 ] nijel commented on YARN-4135: - bq.-1 yarn tests 54m 15s Tests failed in

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747111#comment-14747111 ] Naganarasimha G R commented on YARN-4078: - Thanks for reviewing and committing [~jianhe] &

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Updated] (YARN-4154) Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change

[ https://issues.apache.org/jira/browse/YARN-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4154: Assignee: (was: Akira AJISAKA) > Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change

[jira] [Resolved] (YARN-4154) Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change

[ https://issues.apache.org/jira/browse/YARN-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved YARN-4154. - Resolution: Done Seems to be done by 9c4a6e1 and dba2b6. Thanks Vinod! > Tez Build with hadoop

[jira] [Created] (YARN-4168) Test TestLogAggregationService.testLocalFileDeletionOnDiskFull failing

Steve Loughran created YARN-4168: Summary: Test TestLogAggregationService.testLocalFileDeletionOnDiskFull failing Key: YARN-4168 URL: https://issues.apache.org/jira/browse/YARN-4168 Project: Hadoop

[jira] [Assigned] (YARN-4169) jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels

[ https://issues.apache.org/jira/browse/YARN-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-4169: --- Assignee: Naganarasimha G R > jenkins trunk+java build failed in

[jira] [Updated] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4034: Attachment: 0004-YARN-4034.patch > Render cluster Max Priority in scheduler metrics in RM

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768846#comment-14768846 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #396 (See

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747317#comment-14747317 ] Hadoop QA commented on YARN-4009: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4155) TestLogAggregationService.testLogAggregationServiceWithInterval failing

[ https://issues.apache.org/jira/browse/YARN-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747331#comment-14747331 ] Hadoop QA commented on YARN-4155: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4169) jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels

[ https://issues.apache.org/jira/browse/YARN-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747332#comment-14747332 ] Steve Loughran commented on YARN-4169: -- This may be a transient race condition, but it is caused by

[jira] [Commented] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747356#comment-14747356 ] Hadoop QA commented on YARN-4034: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768858#comment-14768858 ] Hudson commented on YARN-4078: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #379 (See

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768859#comment-14768859 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #379 (See

[jira] [Updated] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4009: Attachment: YARN-4009.002.patch Uploaded a newer version of the patch with some documentation fixed.

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747271#comment-14747271 ] Hudson commented on YARN-4078: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #395 (See

[jira] [Created] (YARN-4169) jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels

Steve Loughran created YARN-4169: Summary: jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels Key: YARN-4169 URL: https://issues.apache.org/jira/browse/YARN-4169 Project: Hadoop YARN

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747373#comment-14747373 ] Hudson commented on YARN-4078: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2318 (See

[jira] [Updated] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-261: --- Attachment: 0001-YARN-261.patch > Ability to kill AM attempts > --- > >

[jira] [Commented] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747384#comment-14747384 ] Rohith Sharma K S commented on YARN-261: Updated the rebased patch.. I have verified the patch in

[jira] [Commented] (YARN-4078) getPendingResourceRequestForAttempt is present in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

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

[jira] [Commented] (YARN-4169) jenkins trunk+java build failed in TestNodeStatusUpdaterForLabels

[ https://issues.apache.org/jira/browse/YARN-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747354#comment-14747354 ] Naganarasimha G R commented on YARN-4169: - Hi [~steve_l] This test is passing locally i will try to

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747353#comment-14747353 ] Brahma Reddy Battula commented on YARN-3433: [~ste...@apache.org] thanks for committing!! >

[jira] [Created] (YARN-4170) AM need to be notified with priority in AllocateResponse

Sunil G created YARN-4170: - Summary: AM need to be notified with priority in AllocateResponse Key: YARN-4170 URL: https://issues.apache.org/jira/browse/YARN-4170 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-4167) NPE on RMActiveServices#serviceStop when store is null

[ https://issues.apache.org/jira/browse/YARN-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4167: --- Priority: Minor (was: Major) > NPE on RMActiveServices#serviceStop when store is null >

[jira] [Updated] (YARN-4167) NPE on RMActiveServices#serviceStop when store is null

[ https://issues.apache.org/jira/browse/YARN-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4167: --- Attachment: 0001-YARN-4167.patch Its an improvement . > NPE on RMActiveServices#serviceStop

[jira] [Commented] (YARN-4167) NPE on RMActiveServices#serviceStop when store is null

[ https://issues.apache.org/jira/browse/YARN-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747275#comment-14747275 ] Bibin A Chundatt commented on YARN-4167: Attaching patch for the same . Please review > NPE on

[jira] [Updated] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3212: - Attachment: YARN-3212-v6.2.patch The unit test failure should be unrelated. Fix whitespace issue in v6.2

[jira] [Updated] (YARN-4155) TestLogAggregationService.testLogAggregationServiceWithInterval failing

[ https://issues.apache.org/jira/browse/YARN-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4155: --- Attachment: 0001-YARN-4155.patch Attaching same patch again to trigger jenkins >

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14747313#comment-14747313 ] Hudson commented on YARN-3433: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #403 (See

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

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

[jira] [Updated] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4009: Attachment: YARN-4009.003.patch Uploaded a new version of the patch that moves the filter into

[jira] [Commented] (YARN-4165) An outstanding container request makes all nodes to be reserved causing all jobs pending

[ https://issues.apache.org/jira/browse/YARN-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768915#comment-14768915 ] Jason Lowe commented on YARN-4165: -- Is this with the fair scheduler? I don't believe the capacity

[jira] [Resolved] (YARN-306) FIFO scheduler doesn't respect changing job priority

[ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-306. - Resolution: Won't Fix bq. Thinking that it may violate FIFO scheduling policy. Well if we're worried about

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768994#comment-14768994 ] Jason Lowe commented on YARN-4141: -- Thanks for updating the patch. One last nit: the EnumSets were using

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14769010#comment-14769010 ] Hadoop QA commented on YARN-3212: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790529#comment-14790529 ] Hadoop QA commented on YARN-4009: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790533#comment-14790533 ] Hudson commented on YARN-3433: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2319 (See

[jira] [Updated] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4009: Attachment: YARN-4009.004.patch Fixed findbugs warning. > CORS support for ResourceManager REST API

[jira] [Updated] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-4148: --- Attachment: YARN-4148.001.patch > When killing app, RM releases app's resource before they are released by NM

[jira] [Commented] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790730#comment-14790730 ] Jun Gong commented on YARN-4148: Attach a new patch. Add a new config to specify whether permits RM

[jira] [Commented] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790611#comment-14790611 ] Hadoop QA commented on YARN-261: \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-306) FIFO scheduler doesn't respect changing job priority

[ https://issues.apache.org/jira/browse/YARN-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790676#comment-14790676 ] Rohith Sharma K S commented on YARN-306: Agree for on-demand implementing priority support in FIFO

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790688#comment-14790688 ] Varun Saxena commented on YARN-2902: bq. Container localizers should already have the concept of

[jira] [Commented] (YARN-3212) RMNode State Transition Update with DECOMMISSIONING state

[ https://issues.apache.org/jira/browse/YARN-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791007#comment-14791007 ] Wangda Tan commented on YARN-3212: -- Patch looks good, thanks [~djp]. Will commit in a few days if no

[jira] [Updated] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4074: -- Attachment: YARN-4074-YARN-2928.POC.006.patch v.6 POC patch posted. Renamed

[jira] [Reopened] (YARN-4154) Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change

[ https://issues.apache.org/jira/browse/YARN-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-4154: --- > Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change >

[jira] [Resolved] (YARN-4154) Tez Build with hadoop 2.6.1 fails due to MiniYarnCluster change

[ https://issues.apache.org/jira/browse/YARN-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-4154. --- Resolution: Duplicate Tx [~ajisakaa], not sure how I missed it earlier, I was

[jira] [Updated] (YARN-2928) YARN Timeline Service: Next generation

[ https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-2928: - Assignee: Sangjin Lee (was: Vrushali C) > YARN Timeline Service: Next generation >

[jira] [Commented] (YARN-4129) Refactor the SystemMetricPublisher in RM to better support newer events

[ https://issues.apache.org/jira/browse/YARN-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790872#comment-14790872 ] Naganarasimha G R commented on YARN-4129: - Hi [~djp], Can you take a look at this patch ? >

[jira] [Commented] (YARN-4148) When killing app, RM releases app's resource before they are released by NM

[ https://issues.apache.org/jira/browse/YARN-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790887#comment-14790887 ] Hadoop QA commented on YARN-4148: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4129) Refactor the SystemMetricPublisher in RM to better support newer events

[ https://issues.apache.org/jira/browse/YARN-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790889#comment-14790889 ] Junping Du commented on YARN-4129: -- Sure. I put this on my review queue and will look at it after settle

[jira] [Updated] (YARN-4157) Merge YARN-1197 back to trunk

[ https://issues.apache.org/jira/browse/YARN-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4157: - Attachment: YARN-1197.diff.4.patch Attached ver.4 patch, sync to latest trunk and fixed findbugs/javac

[jira] [Created] (YARN-4173) Figure out which ones are the final values for metrics

Vrushali C created YARN-4173: Summary: Figure out which ones are the final values for metrics Key: YARN-4173 URL: https://issues.apache.org/jira/browse/YARN-4173 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-2928) YARN Timeline Service: Next generation

[ https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-2928: Assignee: Vrushali C (was: Sangjin Lee) > YARN Timeline Service: Next generation >

[jira] [Commented] (YARN-4163) Audit getQueueInfo and getApplications calls

[ https://issues.apache.org/jira/browse/YARN-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790980#comment-14790980 ] Hadoop QA commented on YARN-4163: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791024#comment-14791024 ] Hadoop QA commented on YARN-4009: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791044#comment-14791044 ] Wangda Tan commented on YARN-4140: -- [~bibinchundatt], bq. The request order ANY will not be always the

[jira] [Updated] (YARN-4171) Resolve findbugs/javac warnings in YARN-1197 branch

[ https://issues.apache.org/jira/browse/YARN-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4171: - Attachment: YARN-4171-YARN-1197.1.patch Attached ver.1 patch. > Resolve findbugs/javac warnings in

[jira] [Commented] (YARN-3816) [Aggregation] App-level aggregation and accumulation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791012#comment-14791012 ] Junping Du commented on YARN-3816: -- Thanks Naga, Varun and Li for review and comments! Let me address them

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790830#comment-14790830 ] Varun Saxena commented on YARN-4074: The patch looks fine to me. I tested some parts related to flow as

[jira] [Commented] (YARN-4172) Extend DominantResourceCalculator to account for all resources

[ https://issues.apache.org/jira/browse/YARN-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790861#comment-14790861 ] Hadoop QA commented on YARN-4172: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790948#comment-14790948 ] Sangjin Lee commented on YARN-4074: --- Thanks for your comments [~varun_saxena]! bq. This I guess is to

[jira] [Commented] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14790987#comment-14790987 ] Joep Rottinghuis commented on YARN-4062: While discussing flush and compaction with [~vrushalic] I

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791225#comment-14791225 ] Hitesh Shah commented on YARN-4009: --- Couple of questions: {code} if

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791115#comment-14791115 ] Jason Lowe commented on YARN-2902: -- bq. For NM side, currently it does not kill localizers. We can track

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791228#comment-14791228 ] Hitesh Shah commented on YARN-4009: --- [~jeagles] Any comments on the patch? > CORS support for

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791226#comment-14791226 ] Hitesh Shah commented on YARN-4009: --- [~jeagles] ? > CORS support for ResourceManager REST API >

[jira] [Updated] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3985: Attachment: YARN-3985.002.patch All the failed tests passed locally for me. Rerunning the tests >

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791251#comment-14791251 ] Jonathan Eagles commented on YARN-4009: --- I have reviewed the patch and have run with the timeline

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run & flow activity tables

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: (was: YARN-3901-YARN-2928.9.patch) > Populate flow run data in the flow_run & flow

  1   2   >