[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

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

[jira] [Commented] (YARN-2605) [RM HA] Rest api endpoints doing redirect incorrectly

[ https://issues.apache.org/jira/browse/YARN-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501248#comment-14501248 ] Steve Loughran commented on YARN-2605: -- I worry about that testcase; it could be a

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 0009-YARN-2003.patch Support to process Job priority from Submission Context in

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

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

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

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

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

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

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

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

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

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

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

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

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501517#comment-14501517 ] Sunil G commented on YARN-2003: --- Findbugs warnings are not related. Support to process Job

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501557#comment-14501557 ] Jian He commented on YARN-3136: --- [~sunilg], below code in latest patch can suppress the

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

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

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501670#comment-14501670 ] Sunil G commented on YARN-3136: --- Thank you very much [~jianhe] for committing the patch and

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501158#comment-14501158 ] Varun Saxena commented on YARN-2962: A little busy nowadays. The change I suggested