[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&focusedCommentId=14731837#comment-14731837 ] Rohith Sharma K S commented on YARN-261: Thanks [~aklochkov] for information.. :-)

[jira] [Assigned] (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 reassigned YARN-261: -- Assignee: Rohith Sharma K S > Ability to kill AM attempts > --- >

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

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

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731754#comment-14731754 ] Hudson commented on YARN-4024: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2298 (See [htt

[jira] [Assigned] (YARN-4118) Newly submitted app maybe stuck at saving state if store operation failure is ignored in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-4118: - Assignee: Sunil G > Newly submitted app maybe stuck at saving state if store operation failure is > ignor

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731697#comment-14731697 ] Naganarasimha G R commented on YARN-4106: - Thanks for the comments [~leftnoteasy],

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

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

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731693#comment-14731693 ] Kishore Chaliparambil commented on YARN-2884: - The test failure is not related

[jira] [Commented] (YARN-4091) Improvement: Introduce more debug/diagnostics information to detail out scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731689#comment-14731689 ] Wangda Tan commented on YARN-4091: -- I found my above suggestion is a little similar to YAR

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

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

[jira] [Created] (YARN-4118) Newly submitted app maybe stuck at saving state if store operation failure is ignored in ZKRMStateStore

Jian He created YARN-4118: - Summary: Newly submitted app maybe stuck at saving state if store operation failure is ignored in ZKRMStateStore Key: YARN-4118 URL: https://issues.apache.org/jira/browse/YARN-4118

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731681#comment-14731681 ] Xuan Gong commented on YARN-4087: - +1 For the Latest patch. [~djp] Do you have any other co

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Commented] (YARN-4091) Improvement: Introduce more debug/diagnostics information to detail out scheduler activity

[ https://issues.apache.org/jira/browse/YARN-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731679#comment-14731679 ] Wangda Tan commented on YARN-4091: -- Thanks folks working on this design [~sunilg]/[~zhigu

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Attachment: YARN-4087.6.patch > Followup fixes after YARN-2019 regarding RM behavior when state-store error > oc

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Attachment: (was: YARN-4087.6.patch) > Followup fixes after YARN-2019 regarding RM behavior when state-store

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Description: Several fixes: 1. Set YARN_FAIL_FAST to be false by default, since this makes more sense in product

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731675#comment-14731675 ] Jian He commented on YARN-4087: --- Had some offline discussion with Vinod and Xuan, simply igno

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Attachment: YARN-4087.6.patch > Followup fixes after YARN-2019 regarding RM behavior when state-store error > oc

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731654#comment-14731654 ] Sangjin Lee commented on YARN-3901: --- (2) colliding puts in the co-processor We found anot

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731651#comment-14731651 ] Li Lu commented on YARN-3901: - [~sjlee0] sure, then let's keep all the work here! > Populate

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731650#comment-14731650 ] Sangjin Lee commented on YARN-3901: --- [~gtCarrera9], I think we're not far off actually. I

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731648#comment-14731648 ] Sangjin Lee commented on YARN-3901: --- (1) FlowScanner cell order issue When I added the re

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731639#comment-14731639 ] Li Lu commented on YARN-3901: - Hi [~vrushalic], since part of this JIRA is blocking the web UI

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731633#comment-14731633 ] Sangjin Lee commented on YARN-3901: --- I went through the code by myself, and also with [~v

[jira] [Commented] (YARN-4083) Add a discovery mechanism for the scheduler address

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731631#comment-14731631 ] Allen Wittenauer commented on YARN-4083: How does this work when the container is a

[jira] [Updated] (YARN-4117) End to end unit test with mini YARN cluster for AMRMProxy Service

[ https://issues.apache.org/jira/browse/YARN-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil updated YARN-4117: Description: YARN-2884 introduces a proxy between AM and RM. This JIRA proposes an en

[jira] [Assigned] (YARN-4117) End to end unit test with mini YARN cluster for AMRMProxy Service

[ https://issues.apache.org/jira/browse/YARN-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil reassigned YARN-4117: --- Assignee: Kishore Chaliparambil (was: Subru Krishnan) > End to end unit test

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731620#comment-14731620 ] Wangda Tan commented on YARN-4106: -- [~bibinchundatt], Thanks for update, Some comments: -

[jira] [Updated] (YARN-4117) End to end unit test with mini YARN cluster for AMRMProxy Service

[ https://issues.apache.org/jira/browse/YARN-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil updated YARN-4117: Description: (was: Today many apps like Distributed Shell, REEF, etc rely on the

[jira] [Created] (YARN-4117) End to end unit test with mini YARN cluster for AMRMProxy Service

Kishore Chaliparambil created YARN-4117: --- Summary: End to end unit test with mini YARN cluster for AMRMProxy Service Key: YARN-4117 URL: https://issues.apache.org/jira/browse/YARN-4117 Project:

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Updated] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3635: - Attachment: YARN-3635.7.patch Rebased to latest trunk (ver.7) > Get-queue-mapping should be a common inter

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

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

[jira] [Commented] (YARN-4081) Add support for multiple resource types in the Resource class

[ https://issues.apache.org/jira/browse/YARN-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731561#comment-14731561 ] Wangda Tan commented on YARN-4081: -- Thanks for update, [~vvasudev]. Few comments, Regardi

[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.003.patch POC v.3 patch posted. Key changes include - switched from

[jira] [Updated] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil updated YARN-2884: Attachment: YARN-2884-V13.patch Fixed the one findbug issue that was found in the pat

[jira] [Updated] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-1651: - Attachment: YARN-1651-3.YARN-1197.patch Attached ver.3 patch, also synchronized repository to latest trunk.

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731505#comment-14731505 ] Wangda Tan commented on YARN-1651: -- Hi Meng, Thanks for comments: bq. We probably need to

[jira] [Commented] (YARN-2410) Nodemanager ShuffleHandler can possible exhaust file descriptors

[ https://issues.apache.org/jira/browse/YARN-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731501#comment-14731501 ] Jason Lowe commented on YARN-2410: -- Thanks for the patch, Kuhu! Do we really need getShuf

[jira] [Commented] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER

[ https://issues.apache.org/jira/browse/YARN-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731454#comment-14731454 ] Wangda Tan commented on YARN-4113: -- [~sunilg]. Thanks, please go ahead! > RM should respe

[jira] [Commented] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

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

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

[jira] [Commented] (YARN-3676) Disregard 'assignMultiple' directive while scheduling apps with NODE_LOCAL resource requests

[ https://issues.apache.org/jira/browse/YARN-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731244#comment-14731244 ] Anubhav Dhoot commented on YARN-3676: - Thanks [~asuresh] for working on this. I see the

[jira] [Updated] (YARN-4081) Add support for multiple resource types in the Resource class

[ https://issues.apache.org/jira/browse/YARN-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4081: Attachment: YARN-4081-YARN-3926.005.patch [~leftnoteasy] pointed out that the current patch allows NO

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

[jira] [Created] (YARN-4116) refactor ColumnHelper read* methods

Sangjin Lee created YARN-4116: - Summary: refactor ColumnHelper read* methods Key: YARN-4116 URL: https://issues.apache.org/jira/browse/YARN-4116 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

[ https://issues.apache.org/jira/browse/YARN-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4115: Attachment: YARN-4115.001.patch Change the default log level to Debug > Reduce loglevel of Container

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

[ https://issues.apache.org/jira/browse/YARN-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731203#comment-14731203 ] Hudson commented on YARN-4105: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #346 (See

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731192#comment-14731192 ] Wangda Tan commented on YARN-4108: -- [~mding], Agree, so far I haven't considered about ho

[jira] [Created] (YARN-4115) Reduce loglevel of ContainerManagementProtocolProxy to Debug

Anubhav Dhoot created YARN-4115: --- Summary: Reduce loglevel of ContainerManagementProtocolProxy to Debug Key: YARN-4115 URL: https://issues.apache.org/jira/browse/YARN-4115 Project: Hadoop YARN

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731183#comment-14731183 ] Wangda Tan commented on YARN-4108: -- [~sunilg], bq. Or is there any other advantage of mak

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731178#comment-14731178 ] Jian He commented on YARN-4087: --- thanks Junping ! I ran the timeout test locally, passing fin

[jira] [Commented] (YARN-4059) Preemption should delay assignments back to the preempted queue

[ https://issues.apache.org/jira/browse/YARN-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731176#comment-14731176 ] Wangda Tan commented on YARN-4059: -- [~jlowe], Thanks again! I think they're all very good

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731173#comment-14731173 ] Vrushali C commented on YARN-3901: -- Thanks [~djp] , appreciate the feedback! I too am figu

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

[ https://issues.apache.org/jira/browse/YARN-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731157#comment-14731157 ] Hudson commented on YARN-4105: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2295 (See [htt

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731135#comment-14731135 ] Junping Du commented on YARN-4087: -- Hi [~jianhe], thanks for the patch! Can you confirm th

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

[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&focusedCommentId=14731080#comment-14731080 ] Andrey Klochkov commented on YARN-261: -- [~rohithsharma], please feel free to reassign t

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

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Klochkov reassigned YARN-261: Assignee: (was: Andrey Klochkov) > Ability to kill AM attempts >

[jira] [Updated] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brook Zhou updated YARN-3223: - Attachment: (was: YARN-3223-v0.patch) > Resource update during NM graceful decommission > -

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14731056#comment-14731056 ] Junping Du commented on YARN-3901: -- Thanks Vrushali for updating the patch. This is a grea

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731048#comment-14731048 ] MENG DING commented on YARN-4108: - Hi, [~leftnoteasy] I also feel that the logic you propo

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730991#comment-14730991 ] Kishore Chaliparambil commented on YARN-2884: - I investigated the Findbug and t

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

[jira] [Commented] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

[ https://issues.apache.org/jira/browse/YARN-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730906#comment-14730906 ] Jason Lowe commented on YARN-4105: -- Test failures are unrelated. Committing this. > Capa

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730887#comment-14730887 ] Jason Lowe commented on YARN-3942: -- bq. Since we know the file size to be read, could we r

[jira] [Commented] (YARN-4059) Preemption should delay assignments back to the preempted queue

[ https://issues.apache.org/jira/browse/YARN-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730856#comment-14730856 ] Jason Lowe commented on YARN-4059: -- I think at a high level that can work, since we can us

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

[ https://issues.apache.org/jira/browse/YARN-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730759#comment-14730759 ] Hudson commented on YARN-4103: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2294 (See [htt

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Updated] (YARN-4109) Exception on RM scheduler page loading with labels

[ https://issues.apache.org/jira/browse/YARN-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4109: --- Description: Configure node label and load scheduler Page On each reload of the page the below

[jira] [Updated] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4106: --- Attachment: 0004-YARN-4106.patch Attaching patch again after checkstyle fix. > NodeLabels for

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

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

[jira] [Created] (YARN-4114) In RM REST API for cluster/scheduler nodelabels in queues not listed properly

Bibin A Chundatt created YARN-4114: -- Summary: In RM REST API for cluster/scheduler nodelabels in queues not listed properly Key: YARN-4114 URL: https://issues.apache.org/jira/browse/YARN-4114 Projec

[jira] [Updated] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4110: Attachment: YARN-4110_1.patch Attached the patch Please review > RMappImpl and RmAppAttemptImpl should override hash

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

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

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

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