[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.2.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684092#comment-13684092 ] Xuan Gong commented on YARN-727: 1.Add a new field String applicationType into

[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.3.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684104#comment-13684104 ] Maysam Yabandeh commented on YARN-779: -- Thanks [~sandyr]. Let me run by you my

[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=13684136#comment-13684136 ] Maysam Yabandeh commented on YARN-659: -- But, it seems that FileSystemRMStateStore uses

[jira] [Commented] (YARN-639) Make AM of Distributed Shell Use NMClient

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

[jira] [Commented] (YARN-821) Rename FinishApplicationMasterRequest.setFinishApplicationStatus to setFinalApplicationStatus to be consistent with getter

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

[jira] [Commented] (YARN-806) Move ContainerExitStatus from yarn.api to yarn.api.records

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

[jira] [Commented] (YARN-782) vcores-pcores ratio functions differently from vmem-pmem ratio in misleading way

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

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

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

[jira] [Commented] (YARN-811) Add a set of final _init/_start/_stop methods to CompositeService

[ https://issues.apache.org/jira/browse/YARN-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684165#comment-13684165 ] Steve Loughran commented on YARN-811: - Siddarth -I see. I went through all the

[jira] [Commented] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684173#comment-13684173 ] Steve Loughran commented on YARN-804: - # code calls init() or start() on a composite

[jira] [Commented] (YARN-821) Rename FinishApplicationMasterRequest.setFinishApplicationStatus to setFinalApplicationStatus to be consistent with getter

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

[jira] [Commented] (YARN-806) Move ContainerExitStatus from yarn.api to yarn.api.records

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

[jira] [Commented] (YARN-782) vcores-pcores ratio functions differently from vmem-pmem ratio in misleading way

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

[jira] [Commented] (YARN-639) Make AM of Distributed Shell Use NMClient

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

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

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

[jira] [Commented] (YARN-789) Enable zero capabilities resource requests in fair scheduler

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

[jira] [Commented] (YARN-821) Rename FinishApplicationMasterRequest.setFinishApplicationStatus to setFinalApplicationStatus to be consistent with getter

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

[jira] [Commented] (YARN-806) Move ContainerExitStatus from yarn.api to yarn.api.records

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

[jira] [Commented] (YARN-639) Make AM of Distributed Shell Use NMClient

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

[jira] [Commented] (YARN-782) vcores-pcores ratio functions differently from vmem-pmem ratio in misleading way

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

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684249#comment-13684249 ] Sandy Ryza commented on YARN-779: - [~maysamyabandeh], I follow you until the end. What API

[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.4.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684251#comment-13684251 ] Xuan Gong commented on YARN-727: Add YarnConfiguration.All_APPLICATION_TYPE to list all

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

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

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684413#comment-13684413 ] Sandy Ryza commented on YARN-779: - The MR AM has solved this problem purely on the AM side

[jira] [Updated] (YARN-781) Expose LOGDIR that containers should use for logging

[ https://issues.apache.org/jira/browse/YARN-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-781: - Attachment: YARN-781.3.patch new patch exposed the containerLogDirs instead of the log base dirs.

[jira] [Commented] (YARN-781) Expose LOGDIR that containers should use for logging

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

[jira] [Created] (YARN-823) Move RMAdmin from yarn.client to yarn.client.cli and rename as RMAdminCLI

Jian He created YARN-823: Summary: Move RMAdmin from yarn.client to yarn.client.cli and rename as RMAdminCLI Key: YARN-823 URL: https://issues.apache.org/jira/browse/YARN-823 Project: Hadoop YARN

[jira] [Updated] (YARN-823) Move RMAdmin from yarn.client to yarn.client.cli and rename as RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-823: - Attachment: YARN-823.patch simple eclipse move and rename Move RMAdmin from yarn.client to

[jira] [Commented] (YARN-823) Move RMAdmin from yarn.client to yarn.client.cli and rename as RMAdminCLI

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

[jira] [Commented] (YARN-781) Expose LOGDIR that containers should use for logging

[ https://issues.apache.org/jira/browse/YARN-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684431#comment-13684431 ] Vinod Kumar Vavilapalli commented on YARN-781: -- Looks good, +1. Checking this

[jira] [Commented] (YARN-781) Expose LOGDIR that containers should use for logging

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

[jira] [Commented] (YARN-823) Move RMAdmin from yarn.client to yarn.client.cli and rename as RMAdminCLI

[ https://issues.apache.org/jira/browse/YARN-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684443#comment-13684443 ] Karthik Kambatla commented on YARN-823: --- To preserve history, an svn mv followed by

[jira] [Updated] (YARN-693) Sending NMToken to AM on allocate call

[ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-693: --- Attachment: YARN-693-20130615.patch Sending NMToken to AM on allocate call

[jira] [Commented] (YARN-693) Sending NMToken to AM on allocate call

Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: YARN-693-20130610.patch, YARN-693-20130613.patch, YARN-693-20130614.1.patch, YARN-693-20130615.patch This is part of YARN-613. As per the updated design, AM will receive per NM, NMToken in following

[jira] [Commented] (YARN-610) ClientToken should not be set in the environment

[ https://issues.apache.org/jira/browse/YARN-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684533#comment-13684533 ] Omkar Vinit Joshi commented on YARN-610: patch submitted should be applied on top of

[jira] [Created] (YARN-824) Add static factory to yarn client lib interface and change it to abstract class

Jian He created YARN-824: Summary: Add static factory to yarn client lib interface and change it to abstract class Key: YARN-824 URL: https://issues.apache.org/jira/browse/YARN-824 Project: Hadoop YARN

[jira] [Commented] (YARN-35) Move to per-node RM-NM secrets

[ https://issues.apache.org/jira/browse/YARN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684537#comment-13684537 ] Omkar Vinit Joshi commented on YARN-35: --- * I think we should make it configurable if

[jira] [Commented] (YARN-693) Sending NMToken to AM on allocate call

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12588000/YARN-693-20130615.patch 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 4

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684539#comment-13684539 ] Hitesh Shah commented on YARN-727: -- @Xuan, shouldn't the absence of application type ( i.e.

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684541#comment-13684541 ] Xuan Gong commented on YARN-727: Yes, that is the better way to do it. Thanks for the

[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.5.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684548#comment-13684548 ] Bikas Saha commented on YARN-779: - That API is AMRMClient.removeContainerRequest().

[jira] [Updated] (YARN-825) Fix yarn-common javadoc annotations

[ https://issues.apache.org/jira/browse/YARN-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-825: - Attachment: YARN-825-20130615.txt Attaching a patch that I worked on with help

[jira] [Commented] (YARN-825) Fix yarn-common javadoc annotations

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12588004/YARN-825-20130615.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include

[jira] [Commented] (YARN-693) Sending NMToken to AM on allocate call

: Omkar Vinit Joshi Fix For: 2.1.0-beta Attachments: YARN-693-20130610.patch, YARN-693-20130613.patch, YARN-693-20130614.1.patch, YARN-693-20130615.patch This is part of YARN-613. As per the updated design, AM will receive per NM, NMToken in following scenarios * AM

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

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

[jira] [Commented] (YARN-610) ClientToken should not be set in the environment

[ https://issues.apache.org/jira/browse/YARN-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684562#comment-13684562 ] Vinod Kumar Vavilapalli commented on YARN-610: -- bq. Now instead of sharing it

[jira] [Updated] (YARN-694) Start using NMTokens to authenticate all communication with NM

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-694: - Summary: Start using NMTokens to authenticate all communication with NM (was: AM

[jira] [Created] (YARN-826) Move Clock/SystemClock to util package

Zhijie Shen created YARN-826: Summary: Move Clock/SystemClock to util package Key: YARN-826 URL: https://issues.apache.org/jira/browse/YARN-826 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-826) Move Clock/SystemClock to util package

[ https://issues.apache.org/jira/browse/YARN-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-826: - Attachment: YARN-826.1.patch Move Clock/SystemClock, patch needs to rebase when YARN-825 is checked in