[jira] [Commented] (YARN-629) Make YarnRemoteException not be rooted at IOException

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647272#comment-13647272 ] Vinod Kumar Vavilapalli commented on YARN-629: -- bq. YarnRemoteException is not

[jira] [Commented] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647263#comment-13647263 ] Vinod Kumar Vavilapalli commented on YARN-613: -- bq. I just have general concern

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

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

[jira] [Commented] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647242#comment-13647242 ] Vinod Kumar Vavilapalli commented on YARN-617: -- bq. Are you saying the goal is

[jira] [Updated] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Attachment: YARN-18-v6.1.patch Address minor javadoc issue in v6.1 patch. > Make locatlity in

[jira] [Commented] (YARN-629) Make YarnRemoteException not be rooted at IOException

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647229#comment-13647229 ] Xuan Gong commented on YARN-629: bq:Need a specific test which validates that the final exce

[jira] [Commented] (YARN-629) Make YarnRemoteException not be rooted at IOException

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647228#comment-13647228 ] Xuan Gong commented on YARN-629: bq:Need a specific test which validates that the final exce

[jira] [Commented] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647211#comment-13647211 ] Omkar Vinit Joshi commented on YARN-617: I am attaching the patch. (Junit tests not

[jira] [Updated] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-617: --- Attachment: YARN-617.20130501.1.patch > In unsercure mode, AM can fake resource requirement

[jira] [Updated] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-617: --- Attachment: YARN-617.20130501.patch > In unsercure mode, AM can fake resource requirements

[jira] [Assigned] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-617: -- Assignee: Omkar Vinit Joshi (was: Vinod Kumar Vavilapalli) > In unsercure mode, AM c

[jira] [Updated] (YARN-638) Add RMDelegationTokens back to DelegationTokenSecretManager after RM Restart

[ https://issues.apache.org/jira/browse/YARN-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-638: - Description: This is missed in YARN-581. After RM restart, RMDelegationTokens need to be added both in DelegationTo

[jira] [Updated] (YARN-606) negative queue metrics "apps Failed"

[ https://issues.apache.org/jira/browse/YARN-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou updated YARN-606: --- Assignee: nemon lou > negative queue metrics "apps Failed" > - > >

[jira] [Updated] (YARN-638) Add RMDelegationTokens back to DelegationTokenSecretManager after RM Restart

[ https://issues.apache.org/jira/browse/YARN-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-638: - Summary: Add RMDelegationTokens back to DelegationTokenSecretManager after RM Resta

[jira] [Moved] (YARN-641) Make AMLauncher in RM Use NMClient

[ https://issues.apache.org/jira/browse/YARN-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen moved HADOOP-9538 to YARN-641: -- Key: YARN-641 (was: HADOOP-9538) Project: Hadoop YARN (was: Hadoop Commo

[jira] [Created] (YARN-640) Make AM of M/R Use NMClient

Zhijie Shen created YARN-640: Summary: Make AM of M/R Use NMClient Key: YARN-640 URL: https://issues.apache.org/jira/browse/YARN-640 Project: Hadoop YARN Issue Type: Bug Reporter: Zhi

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

[ https://issues.apache.org/jira/browse/YARN-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-639: - Environment: (was: YARN-422 adds ) > Make AM of Distributed Shell Use NMClient > --

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

[ https://issues.apache.org/jira/browse/YARN-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-639: - Description: YARN-422 adds NMClient. AM of Distributed Shell should use it instead of using ContainerManage

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

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

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

[ https://issues.apache.org/jira/browse/YARN-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-639: Assignee: Zhijie Shen > Make AM of Distributed Shell Use NMClient > -

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

[ https://issues.apache.org/jira/browse/YARN-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-639: - Description: YARN-422 ads > Make AM of Distributed Shell Use NMClient > ---

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

Zhijie Shen created YARN-639: Summary: Make AM of Distributed Shell Use NMClient Key: YARN-639 URL: https://issues.apache.org/jira/browse/YARN-639 Project: Hadoop YARN Issue Type: Bug En

[jira] [Updated] (YARN-422) Add NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-422: - Description: Create a simple wrapper over the ContainerManager protocol to provide hide the details of the

[jira] [Updated] (YARN-422) Add NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-422: - Summary: Add NM client library (was: Add AM-NM client library) > Add NM client library > -

[jira] [Updated] (YARN-618) Modify RM_INVALID_IDENTIFIER to a -ve number

[ https://issues.apache.org/jira/browse/YARN-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-618: - Attachment: YARN-618.3-branch-2.patch The patch didn't apply cleanly against branch

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647089#comment-13647089 ] Xuan Gong commented on YARN-513: The new patch is YARN.513.5.patch > Create

[jira] [Updated] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-513: --- Attachment: YARN.513.5.patch > Create common proxy client for communicating with RM > -

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647085#comment-13647085 ] Xuan Gong commented on YARN-513: The new patch includes: 1. remove RMClient, create RMProxy,

[jira] [Commented] (YARN-618) Modify RM_INVALID_IDENTIFIER to a -ve number

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

[jira] [Commented] (YARN-618) Modify RM_INVALID_IDENTIFIER to a -ve number

[ https://issues.apache.org/jira/browse/YARN-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647062#comment-13647062 ] Vinod Kumar Vavilapalli commented on YARN-618: -- +1, checking it in.

[jira] [Commented] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646993#comment-13646993 ] Chris Riccomini commented on YARN-614: -- bq. One solution could be to move the check fro

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646914#comment-13646914 ] Xuan Gong commented on YARN-513: Actually, the RMClient.invoke() can be removed. I followed

[jira] [Commented] (YARN-582) Restore appToken for app attempt after RM restart

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

[jira] [Updated] (YARN-582) Restore appToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-582: - Attachment: YARN-582.3.patch > Restore appToken for app attempt after RM restart >

[jira] [Commented] (YARN-582) Restore appToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646806#comment-13646806 ] Jian He commented on YARN-582: -- new patch addressed last comments > Restore ap

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

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

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646652#comment-13646652 ] Junping Du commented on YARN-18: Thanks Luke for explanation. Hey Arun ([~acmurthy]), I just

[jira] [Updated] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Attachment: YARN-18-v6.patch Sync patch to latest trunk which keep consist with doc just attached.

[jira] [Updated] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Attachment: Pluggable topologies with NodeGroup for YARN.pdf Implementation doc for NodeGroup layer support in Y

[jira] [Commented] (YARN-617) In unsercure mode, AM can fake resource requirements

[ https://issues.apache.org/jira/browse/YARN-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646572#comment-13646572 ] Daryn Sharp commented on YARN-617: -- bq. we are trying to change the auth to use AMTokens an

[jira] [Commented] (YARN-613) Create NM proxy per NM instead of per container

[ https://issues.apache.org/jira/browse/YARN-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646558#comment-13646558 ] Daryn Sharp commented on YARN-613: -- I just have general concerns with assuming the entire h

[jira] [Commented] (YARN-422) Add AM-NM client library

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

[jira] [Updated] (YARN-422) Add AM-NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-422: - Attachment: YARN-422.2.patch Try to fix the test failure. The problem seems that the mockNMClient is change

[jira] [Commented] (YARN-422) Add AM-NM client library

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

[jira] [Updated] (YARN-422) Add AM-NM client library

[ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-422: - Attachment: YARN-422.1.patch Here's the first patch, which is ready for review. Based on the previous defi

[jira] [Commented] (YARN-600) Hook up cgroups CPU settings to the number of virtual cores allocated

[ https://issues.apache.org/jira/browse/YARN-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646436#comment-13646436 ] Sandy Ryza commented on YARN-600: - (by which I mean YARN doesn't give hints to the OS on how

[jira] [Commented] (YARN-600) Hook up cgroups CPU settings to the number of virtual cores allocated

[ https://issues.apache.org/jira/browse/YARN-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646435#comment-13646435 ] Sandy Ryza commented on YARN-600: - I don't believe anything special happens when it's not en