[jira] [Commented] (YARN-1239) Save version information in the state store

[ https://issues.apache.org/jira/browse/YARN-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821050#comment-13821050 ] Tsuyoshi OZAWA commented on YARN-1239: -- IMO, version number should be defined in

[jira] [Commented] (YARN-1239) Save version information in the state store

[ https://issues.apache.org/jira/browse/YARN-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821053#comment-13821053 ] Jian He commented on YARN-1239: --- This is a dead patch, just disregard it. I will put a new

[jira] [Commented] (YARN-1239) Save version information in the state store

[ https://issues.apache.org/jira/browse/YARN-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821060#comment-13821060 ] Tsuyoshi OZAWA commented on YARN-1239: -- [~jianhe], do you mind if I take this JIRA,

[jira] [Commented] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

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

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

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

[jira] [Updated] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1392: - Attachment: YARN-1392-1.patch Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[jira] [Commented] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

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

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

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

[jira] [Updated] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1307: - Attachment: YARN-1307.5.patch Thank you for review, [~jianhe]. Updated patch based on your review

[jira] [Commented] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

[ https://issues.apache.org/jira/browse/YARN-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821155#comment-13821155 ] Junping Du commented on YARN-312: - In v4.1 patch, I already remove parameter of

[jira] [Updated] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1408: -- Attachment: Yarn-1408.1.patch Updated patch against the trunk Preemption caused Invalid State Event: ACQUIRED

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821181#comment-13821181 ] Steve Loughran commented on YARN-1404: -- # I'd be inclined to treat this as a special

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

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

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

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

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

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

[jira] [Commented] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

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

[jira] [Commented] (YARN-1400) yarn.cmd uses HADOOP_RESOURCEMANAGER_OPTS. Should be YARN_RESOURCEMANAGER_OPTS.

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

[jira] [Commented] (YARN-1387) RMWebServices should use ClientRMService for filtering applications

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

[jira] [Commented] (YARN-1395) Distributed shell application master launched with debug flag can hang waiting for external ls process.

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

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821219#comment-13821219 ] Tsuyoshi OZAWA commented on YARN-1307: -- The latest patch doesn't include any tests,

[jira] [Created] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

Tsuyoshi OZAWA created YARN-1409: Summary: NonAggregatingLongHandler can throw RejectedExecutionException Key: YARN-1409 URL: https://issues.apache.org/jira/browse/YARN-1409 Project: Hadoop YARN

[jira] [Commented] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

[ https://issues.apache.org/jira/browse/YARN-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821242#comment-13821242 ] Hudson commented on YARN-1386: -- FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #789 (See

[jira] [Updated] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1409: - Attachment: YARN-1409.1.patch Fixed to check whether ScheduledThreadPoolExecutor is active.

[jira] [Updated] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1409: - Description: This problem is caused by handling APPLICATION_FINISHED events after calling

[jira] [Commented] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

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

[jira] [Commented] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

[ https://issues.apache.org/jira/browse/YARN-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821299#comment-13821299 ] Junping Du commented on YARN-312: - Anyway, this java doc seems not very helpful. Remove it

[jira] [Updated] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

[ https://issues.apache.org/jira/browse/YARN-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-312: Attachment: YARN-312-v5.patch Add updateNodeResource in ResourceManagerAdministrationProtocol

[jira] [Commented] (YARN-1395) Distributed shell application master launched with debug flag can hang waiting for external ls process.

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

[jira] [Commented] (YARN-1400) yarn.cmd uses HADOOP_RESOURCEMANAGER_OPTS. Should be YARN_RESOURCEMANAGER_OPTS.

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

[jira] [Commented] (YARN-1387) RMWebServices should use ClientRMService for filtering applications

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

[jira] [Commented] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

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

[jira] [Commented] (YARN-1400) yarn.cmd uses HADOOP_RESOURCEMANAGER_OPTS. Should be YARN_RESOURCEMANAGER_OPTS.

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

[jira] [Commented] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

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

[jira] [Commented] (YARN-1387) RMWebServices should use ClientRMService for filtering applications

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

[jira] [Commented] (YARN-1395) Distributed shell application master launched with debug flag can hang waiting for external ls process.

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

[jira] [Commented] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

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

[jira] [Updated] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

[ https://issues.apache.org/jira/browse/YARN-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-312: Attachment: YARN-312-v5.1.patch Oops. Just found I fixed the wrong places before (warning is not in request

[jira] [Commented] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821380#comment-13821380 ] Jason Lowe commented on YARN-1409: -- Is it sufficient to only check for scheduler shutdown

[jira] [Commented] (YARN-312) Add updateNodeResource in ResourceManagerAdministrationProtocol

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

[jira] [Commented] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

[ https://issues.apache.org/jira/browse/YARN-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821413#comment-13821413 ] Thomas Graves commented on YARN-1407: - I think it will be fine for backwards

[jira] [Commented] (YARN-1409) NonAggregatingLongHandler can throw RejectedExecutionException

[ https://issues.apache.org/jira/browse/YARN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821437#comment-13821437 ] Tsuyoshi OZAWA commented on YARN-1409: -- Thank you for the review, Jason. I overlooked

[jira] [Updated] (YARN-1386) NodeManager mistakenly loses resources and relocalizes them

[ https://issues.apache.org/jira/browse/YARN-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-1386: -- Fix Version/s: 2.2.1 NodeManager mistakenly loses resources and relocalizes them

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821489#comment-13821489 ] Karthik Kambatla commented on YARN-1307: Went through the patch superficially.

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821510#comment-13821510 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- -1 for this. (my first on

[jira] [Updated] (YARN-1028) Add FailoverProxyProvider like capability to RMProxy

[ https://issues.apache.org/jira/browse/YARN-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1028: --- Attachment: yarn-1028-1.patch Here is a first-cut patch that implements failover based on the

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821586#comment-13821586 ] Vinod Kumar Vavilapalli commented on YARN-674: -- More comments, hopefully the

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821589#comment-13821589 ] Vinod Kumar Vavilapalli commented on YARN-674: -- The other point is the default

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821592#comment-13821592 ] Sandy Ryza commented on YARN-1404: -- [~vinodkv], a lightweight RM is not sufficient because

[jira] [Commented] (YARN-1040) De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container

[ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821597#comment-13821597 ] Alejandro Abdelnur commented on YARN-1040: -- [~bikassaha], if I got it right, you

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821657#comment-13821657 ] Alejandro Abdelnur commented on YARN-1404: -- [~ste...@apache.org] bq. 1. I'd be

[jira] [Commented] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

[ https://issues.apache.org/jira/browse/YARN-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821692#comment-13821692 ] Alejandro Abdelnur commented on YARN-1407: -- Agree with [~tgraves], +1 after doc

[jira] [Commented] (YARN-1241) In Fair Scheduler maxRunningApps does not work for non-leaf queues

[ https://issues.apache.org/jira/browse/YARN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821695#comment-13821695 ] Alejandro Abdelnur commented on YARN-1241: -- patch needs to be rebased, it does not

[jira] [Commented] (YARN-584) In fair scheduler web UI, queues unexpand on refresh

[ https://issues.apache.org/jira/browse/YARN-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821712#comment-13821712 ] Harshit Daga commented on YARN-584: --- bq. Also, maybe rename them to ExpandQueueNode and

[jira] [Resolved] (YARN-920) List of applications at NM web UI is inconsistent with applications at RM UI after RM restart

[ https://issues.apache.org/jira/browse/YARN-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-920. -- Resolution: Cannot Reproduce Not reproducible, as finished apps on NM just get removed List of applications at

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821764#comment-13821764 ] Alejandro Abdelnur commented on YARN-1392: -- Overall looks good. * Javadoc warning

[jira] [Commented] (YARN-1378) Implement a RMStateStore cleaner for deleting application/attempt info

[ https://issues.apache.org/jira/browse/YARN-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821828#comment-13821828 ] Jian He commented on YARN-1378: --- Did the experiment with ZK in my local machine, storing 5000

[jira] [Commented] (YARN-901) Active users field in Resourcemanager scheduler UI gives negative values

[ https://issues.apache.org/jira/browse/YARN-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821866#comment-13821866 ] Jian He commented on YARN-901: -- I'm closing this as not reproducible. Active users field in

[jira] [Commented] (YARN-1239) Save version information in the state store

[ https://issues.apache.org/jira/browse/YARN-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821870#comment-13821870 ] Jian He commented on YARN-1239: --- Thanks for asking, I had already created a patch and can

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821878#comment-13821878 ] Tsuyoshi OZAWA commented on YARN-1307: -- [~kkambatl], thank you for review. OK, I'm

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821881#comment-13821881 ] Sandy Ryza commented on YARN-1392: -- Uploading a patch that addresses these comments.

[jira] [Updated] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1392: - Attachment: YARN-1392-2.patch Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821892#comment-13821892 ] Jian He commented on YARN-1307: --- correct me if I'm wrong, while we are removing attempts, we

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821901#comment-13821901 ] Jian He commented on YARN-659: -- Hi [~ozawa], I noticed that while we are removing app state

[jira] [Commented] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

[ https://issues.apache.org/jira/browse/YARN-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821916#comment-13821916 ] Sandy Ryza commented on YARN-1407: -- Uploading a patch that fixes the test, updates the

[jira] [Updated] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

[ https://issues.apache.org/jira/browse/YARN-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1407: - Attachment: YARN-1407-1.patch apps REST API filters queries by YarnApplicationState, but includes

[jira] [Updated] (YARN-1241) In Fair Scheduler maxRunningApps does not work for non-leaf queues

[ https://issues.apache.org/jira/browse/YARN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1241: - Attachment: YARN-1241-7.patch In Fair Scheduler maxRunningApps does not work for non-leaf queues

[jira] [Commented] (YARN-1241) In Fair Scheduler maxRunningApps does not work for non-leaf queues

[ https://issues.apache.org/jira/browse/YARN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821922#comment-13821922 ] Sandy Ryza commented on YARN-1241: -- Uploaded a rebased patch In Fair Scheduler

[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821933#comment-13821933 ] Jian He commented on YARN-1166: --- bq. The main problem is that QueueMetrics are being driven

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

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

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821950#comment-13821950 ] Alejandro Abdelnur commented on YARN-1392: -- a few final minor things: *

[jira] [Assigned] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-999: --- Assignee: Junping Du In case of long running tasks, reduce node resource should balloon out

[jira] [Commented] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821976#comment-13821976 ] Junping Du commented on YARN-999: - In YARN-311, we get OverCommitTimeout into ResourceOption

[jira] [Commented] (YARN-1241) In Fair Scheduler maxRunningApps does not work for non-leaf queues

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

[jira] [Commented] (YARN-1407) apps REST API filters queries by YarnApplicationState, but includes RMAppStates in response

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

[jira] [Updated] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1392: - Attachment: YARN-1392-3.patch Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822018#comment-13822018 ] Sandy Ryza commented on YARN-1392: -- Uploaded a patch that addresses latest comments.

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822024#comment-13822024 ] Bikas Saha commented on YARN-674: - Increasing the threads without ascertaining if work is

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822026#comment-13822026 ] Omkar Vinit Joshi commented on YARN-674: Thanks [~vinodkv] bq.

[jira] [Updated] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-674: --- Attachment: YARN-674.7.patch Slow or failing DelegationToken renewals on submission itself

[jira] [Commented] (YARN-1378) Implement a RMStateStore cleaner for deleting application/attempt info

[ https://issues.apache.org/jira/browse/YARN-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822030#comment-13822030 ] Bikas Saha commented on YARN-1378: -- Do you think loading application attempts will have

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822034#comment-13822034 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- bq. Vinod Kumar Vavilapalli,

[jira] [Commented] (YARN-291) [Umbrella] Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822052#comment-13822052 ] Cindy Li commented on YARN-291: --- JunPing, I'm trying to find out where you handle different

[jira] [Updated] (YARN-953) [YARN-321] Enable ResourceManager to write history data

[ https://issues.apache.org/jira/browse/YARN-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-953: - Attachment: YARN-953.8.patch bq. history-writer.dispatcher-vector-size -

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822092#comment-13822092 ] Tsuyoshi OZAWA commented on YARN-659: - Hi [~jianhe], ZK doesn't support 'directory

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822098#comment-13822098 ] Tsuyoshi OZAWA commented on YARN-1307: -- Oops, this is my bad. Thank you for pointing

[jira] [Commented] (YARN-1392) Allow sophisticated app-to-queue placement policies in the Fair Scheduler

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

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

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

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822102#comment-13822102 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- On top of what I said, want

[jira] [Commented] (YARN-1307) Rethink znode structure for RM HA

[ https://issues.apache.org/jira/browse/YARN-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822106#comment-13822106 ] Tsuyoshi OZAWA commented on YARN-1307: -- In RMStateStoreTestBase, removeApplicationId

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822107#comment-13822107 ] Bikas Saha commented on YARN-659: - Please look at the API

[jira] [Commented] (YARN-953) [YARN-321] Enable ResourceManager to write history data

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

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822113#comment-13822113 ] Tsuyoshi OZAWA commented on YARN-659: - If version is -1 in the delete command then the

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822120#comment-13822120 ] Tsuyoshi OZAWA commented on YARN-659: - Ah, I misunderstood. Thank you for pointing out,

[jira] [Commented] (YARN-1404) Add support for unmanaged containers

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822124#comment-13822124 ] Bikas Saha commented on YARN-1404: -- It looks like the uber point under discussion here is

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822127#comment-13822127 ] Tsuyoshi OZAWA commented on YARN-659: - [~bikassaha], correct me if I'm wrong. IIUC,

[jira] [Updated] (YARN-1241) In Fair Scheduler maxRunningApps does not work for non-leaf queues

[ https://issues.apache.org/jira/browse/YARN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1241: - Attachment: YARN-1241-8.patch In Fair Scheduler maxRunningApps does not work for non-leaf queues

[jira] [Commented] (YARN-659) RMStateStore's removeApplication APIs should just take an applicationId

[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822134#comment-13822134 ] Bikas Saha commented on YARN-659: - Sorry for now being clear. I was clarifying on no

[jira] [Updated] (YARN-1410) Handle client failover during app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1410: - Description: App submission involves 1) creating appId 2) using that appId to submit an

[jira] [Created] (YARN-1410) Handle client failover during app submission

Bikas Saha created YARN-1410: Summary: Handle client failover during app submission Key: YARN-1410 URL: https://issues.apache.org/jira/browse/YARN-1410 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1410: - Summary: Handle client failover during 2 step client API's like app submission (was: Handle client

  1   2   >