[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692797#comment-13692797 ] Devaraj K commented on YARN-884: we can suggest the user to configure the am expiry interval

[jira] [Updated] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command

[ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-853: --- Summary: maximum-am-resource-percent doesn't work after refreshQueues command (was:

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

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

[jira] [Created] (YARN-886) make APPLICATION_STOP consistent with APPLICATION_INIT

Avner BenHanoch created YARN-886: Summary: make APPLICATION_STOP consistent with APPLICATION_INIT Key: YARN-886 URL: https://issues.apache.org/jira/browse/YARN-886 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

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

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

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

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693057#comment-13693057 ] Karthik Kambatla commented on YARN-884: --- Thanks Devaraj. The default values are okay

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693133#comment-13693133 ] Devaraj K commented on YARN-884: bq.Setting the internal variable to the smaller of the two

[jira] [Commented] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

[ https://issues.apache.org/jira/browse/YARN-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693186#comment-13693186 ] Daryn Sharp commented on YARN-874: -- +1! Tracking YARN/MR test failures

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693216#comment-13693216 ] Chris Riccomini commented on YARN-864: -- Hey Guys, Thanks for all the help. The cluster

[jira] [Commented] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command

[ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693277#comment-13693277 ] Zhijie Shen commented on YARN-853: -- The patch looks almost good, just one small nit: In

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693395#comment-13693395 ] Karthik Kambatla commented on YARN-884: --- I was wondering if there is any disadvantage

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693528#comment-13693528 ] Jian He commented on YARN-864: -- Hi Chris YARN-495 was already committed which deals with

[jira] [Commented] (YARN-869) ResourceManagerAdministrationProtocol should neither be public(yet) nor in yarn.api

[ https://issues.apache.org/jira/browse/YARN-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693541#comment-13693541 ] Vinod Kumar Vavilapalli commented on YARN-869: -- Trying Jenkins again..

[jira] [Commented] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

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

[jira] [Commented] (YARN-869) ResourceManagerAdministrationProtocol should neither be public(yet) nor in yarn.api

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

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693593#comment-13693593 ] Omkar Vinit Joshi commented on YARN-873: I think the client should get an error code

[jira] [Commented] (YARN-554) YARN with security enabled read local block failed

[ https://issues.apache.org/jira/browse/YARN-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693594#comment-13693594 ] Omkar Vinit Joshi commented on YARN-554: is this valid on trunk?

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13693598#comment-13693598 ] Devaraj K commented on YARN-884: It may lead confusion to the user taking the value of one

[jira] [Updated] (YARN-869) ResourceManagerAdministrationProtocol should neither be public(yet) nor in yarn.api

[ https://issues.apache.org/jira/browse/YARN-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-869: - Attachment: YARN-869-20130625.txt This should do

[jira] [Updated] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command

[ https://issues.apache.org/jira/browse/YARN-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K updated YARN-853: --- Attachment: YARN-853-2.patch maximum-am-resource-percent doesn't work after refreshQueues command

[jira] [Commented] (YARN-853) maximum-am-resource-percent doesn't work after refreshQueues command

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

[jira] [Commented] (YARN-869) ResourceManagerAdministrationProtocol should neither be public(yet) nor in yarn.api

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12589704/YARN-869-20130625.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1

[jira] [Resolved] (YARN-885) TestBinaryTokenFile (and others) fail

[ https://issues.apache.org/jira/browse/YARN-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-885. -- Resolution: Duplicate This is fixed by YARN-874.