[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Updated] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

[ https://issues.apache.org/jira/browse/YARN-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-799: --- Assignee: Chris Riccomini CgroupsLCEResourcesHandler tries to write to cgroup.procs

[jira] [Updated] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-846: - Attachment: YARN-846.full.patch resubmit the patch to kick jenkins Move pb Impl from yarn-api to

[jira] [Commented] (YARN-841) Annotate and document AuxService APIs

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

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Updated] (YARN-846) Move pb Impl from yarn-api to yarn-common

[ https://issues.apache.org/jira/browse/YARN-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-846: - Attachment: YARN-846.full.1.patch rebased on latest trunk Move pb Impl from yarn-api to

[jira] [Commented] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

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

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13686549#comment-13686549 ] Omkar Vinit Joshi commented on YARN-694: Fixing about comments. bq.

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.patch Start using NMTokens to authenticate all

[jira] [Commented] (YARN-759) Create Command enum in AllocateResponse

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

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

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

[jira] [Commented] (YARN-839) TestContainerLaunch.testContainerEnvVariables fails on Windows

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

[jira] [Commented] (YARN-822) Rename ApplicationToken to AMRMToken

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

[jira] [Commented] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

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

[jira] [Commented] (YARN-840) Move ProtoUtils to yarn.api.records.pb.impl

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

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Commented] (YARN-805) Fix yarn-api javadoc annotations

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

[jira] [Commented] (YARN-841) Annotate and document AuxService APIs

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

[jira] [Commented] (YARN-834) Review/fix annotations for yarn-client module and clearly differentiate *Async apis

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

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.1.patch Start using NMTokens to authenticate all

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: (was: YARN-694-20130618.patch) Start using NMTokens to authenticate all

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13686656#comment-13686656 ] Hadoop QA commented on YARN-694: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-846) Move pb Impl from yarn-api to yarn-common

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

[jira] [Commented] (YARN-834) Review/fix annotations for yarn-client module and clearly differentiate *Async apis

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

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

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

[jira] [Commented] (YARN-822) Rename ApplicationToken to AMRMToken

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

[jira] [Commented] (YARN-759) Create Command enum in AllocateResponse

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

[jira] [Commented] (YARN-841) Annotate and document AuxService APIs

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

[jira] [Commented] (YARN-799) CgroupsLCEResourcesHandler tries to write to cgroup.procs

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

[jira] [Commented] (YARN-840) Move ProtoUtils to yarn.api.records.pb.impl

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

[jira] [Commented] (YARN-805) Fix yarn-api javadoc annotations

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

[jira] [Updated] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-553: --- Summary: Have YarnClient generate a directly usable ApplicationSubmissionContext (was: Have

[jira] [Commented] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686720#comment-13686720 ] Arun C Murthy commented on YARN-553: I edited jira description to reflect actual intent.

[jira] [Commented] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686737#comment-13686737 ] Arun C Murthy commented on YARN-553: [~kkambatl] Is there a chance you can provide a

[jira] [Commented] (YARN-805) Fix yarn-api javadoc annotations

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

[jira] [Commented] (YARN-841) Annotate and document AuxService APIs

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

[jira] [Commented] (YARN-822) Rename ApplicationToken to AMRMToken

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

[jira] [Commented] (YARN-839) TestContainerLaunch.testContainerEnvVariables fails on Windows

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

[jira] [Commented] (YARN-759) Create Command enum in AllocateResponse

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

[jira] [Commented] (YARN-834) Review/fix annotations for yarn-client module and clearly differentiate *Async apis

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

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

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

[jira] [Commented] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686961#comment-13686961 ] Karthik Kambatla commented on YARN-553: --- Hey [~acmurthy], thanks for taking a look.

[jira] [Commented] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686972#comment-13686972 ] Harsh J commented on YARN-553: -- I'm fine with what Arun's proposed above - a single API call

[jira] [Commented] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686994#comment-13686994 ] Arun C Murthy commented on YARN-553: We'll need to return a struct with both

[jira] [Commented] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687052#comment-13687052 ] Bikas Saha commented on YARN-569: - The correct place for the configs would depend on which

[jira] [Created] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

Hitesh Shah created YARN-848: Summary: Nodemanager does not register with RM using the fully qualified hostname Key: YARN-848 URL: https://issues.apache.org/jira/browse/YARN-848 Project: Hadoop YARN

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Description: If the hostname is misconfigured to not be fully qualified ( i.e. hostname returns foo and

[jira] [Created] (YARN-849) YARN should figure out the hostname instead of expecting it in the Application Register call

Jian He created YARN-849: Summary: YARN should figure out the hostname instead of expecting it in the Application Register call Key: YARN-849 URL: https://issues.apache.org/jira/browse/YARN-849 Project:

[jira] [Updated] (YARN-849) YARN should figure out the App hostname instead of expecting it in the Application Register call

[ https://issues.apache.org/jira/browse/YARN-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-849: - Summary: YARN should figure out the App hostname instead of expecting it in the Application Register call (was:

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Description: If the hostname is misconfigured to not be fully qualified ( i.e. hostname returns foo and

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.2.patch Start using NMTokens to authenticate all

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.3.patch Start using NMTokens to authenticate all

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Attachment: YARN-848.1.patch Nodemanager does not register with RM using the fully qualified hostname

[jira] [Created] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

Jian He created YARN-850: Summary: Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources Key: YARN-850 URL: https://issues.apache.org/jira/browse/YARN-850

[jira] [Updated] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-850: - Attachment: YARN-850.patch trivial rename patch Rename AMRMClient#getClusterAvailableResources,

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.4.patch Start using NMTokens to authenticate all

[jira] [Commented] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687174#comment-13687174 ] Bikas Saha commented on YARN-850: - Will commit when tests pass. Rename

[jira] [Commented] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687172#comment-13687172 ] Bikas Saha commented on YARN-850: - Thanks Jian. This matches the method name with the method

[jira] [Updated] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-850: Affects Version/s: 2.1.0-beta Rename AMRMClient#getClusterAvailableResources,

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

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

[jira] [Commented] (YARN-850) Rename AMRMClient#getClusterAvailableResources, AMRMClientAsync#getClusterAvailableResources to getAvailableResources

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

[jira] [Updated] (YARN-850) Rename getClusterAvailableResources to getAvailableResources in AMRMClients

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-850: Summary: Rename getClusterAvailableResources to getAvailableResources in AMRMClients (was: Rename

[jira] [Updated] (YARN-850) Rename AMRMClient*#getClusterAvailableResources to getAvailableResources

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-850: Summary: Rename AMRMClient*#getClusterAvailableResources to getAvailableResources (was: Rename

[jira] [Commented] (YARN-850) Rename getClusterAvailableResources to getAvailableResources in AMRMClients

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

[jira] [Commented] (YARN-850) Rename getClusterAvailableResources to getAvailableResources in AMRMClients

[ https://issues.apache.org/jira/browse/YARN-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687220#comment-13687220 ] Bikas Saha commented on YARN-850: - Committed to trunk, branch-2 and branch-2.1.beta

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687248#comment-13687248 ] Siddharth Seth commented on YARN-848: - +1. Simple enough patch. Hitesh, could you please

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13687252#comment-13687252 ] Hadoop QA commented on YARN-694: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687251#comment-13687251 ] Vinod Kumar Vavilapalli commented on YARN-848: -- Also, any manual tests to

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13687256#comment-13687256 ] Vinod Kumar Vavilapalli commented on YARN-694: -- This looks good, +1 except for

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.5.patch Start using NMTokens to authenticate all

[jira] [Resolved] (YARN-739) NM startContainer should validate the NodeId

[ https://issues.apache.org/jira/browse/YARN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-739. Resolution: Fixed Fix Version/s: 2.1.0-beta NM startContainer should validate

[jira] [Commented] (YARN-739) NM startContainer should validate the NodeId

[ https://issues.apache.org/jira/browse/YARN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687272#comment-13687272 ] Omkar Vinit Joshi commented on YARN-739: YARN-694 fixes this. closing this

[jira] [Commented] (YARN-739) NM startContainer should validate the NodeId

[ https://issues.apache.org/jira/browse/YARN-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687275#comment-13687275 ] Omkar Vinit Joshi commented on YARN-739: This same check is added for NMToken too.

[jira] [Updated] (YARN-818) YARN application classpath should add $PWD/* in addition to $PWD

[ https://issues.apache.org/jira/browse/YARN-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-818: - Attachment: YARN-818.patch Add $PWD/* to YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH and

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Attachment: YARN-848.2.patch Rebased against YARN-694. Nodemanager does not register

[jira] [Commented] (YARN-575) ContainerManager APIs should be user accessible

[ https://issues.apache.org/jira/browse/YARN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687306#comment-13687306 ] Omkar Vinit Joshi commented on YARN-575: I guess this can be closed now. after

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

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

[jira] [Commented] (YARN-818) YARN application classpath should add $PWD/* in addition to $PWD

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

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Attachment: YARN-848.3.patch Correct patch rebased on YARN-649 Nodemanager does not

[jira] [Updated] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-848: - Attachment: (was: YARN-848.2.patch) Nodemanager does not register with RM using the fully

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13687350#comment-13687350 ] Hadoop QA commented on YARN-694: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13687370#comment-13687370 ] Hudson commented on YARN-694: - Integrated in Hadoop-trunk-Commit #3973 (See

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.patch.yarn-694-branch-2.1-beta Start using NMTokens

[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 ] Omkar Vinit Joshi updated YARN-694: --- Attachment: YARN-694-20130618.patch.branch-2 Start using NMTokens to authenticate all

[jira] [Commented] (YARN-845) RM crash with NPE on NODE_UPDATE

[ https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687382#comment-13687382 ] Mayank Bansal commented on YARN-845: [~arpitgupta] I couldn't reproduce this issue, and

[jira] [Updated] (YARN-845) RM crash with NPE on NODE_UPDATE

[ https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-845: --- Attachment: YARN-845-trunk-draft.patch RM crash with NPE on NODE_UPDATE

[jira] [Resolved] (YARN-820) NodeManager has invalid state transition after error in resource localization

[ https://issues.apache.org/jira/browse/YARN-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal resolved YARN-820. Resolution: Duplicate NodeManager has invalid state transition after error in resource

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

[ https://issues.apache.org/jira/browse/YARN-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687388#comment-13687388 ] Siddharth Seth commented on YARN-848: - +1. Thanks Hitesh. Committing this.

[jira] [Commented] (YARN-848) Nodemanager does not register with RM using the fully qualified hostname

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

[jira] [Updated] (YARN-553) Have YarnClient generate a directly usable ApplicationSubmissionContext

[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-553: -- Attachment: yarn-553-3.patch Patch yarn-553-3.patch that: # removes getNewApplication calls from

[jira] [Created] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

Omkar Vinit Joshi created YARN-851: -- Summary: Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently. Key: YARN-851 URL:

[jira] [Commented] (YARN-851) Share NMTokens using NMTokenCache (api-based) instead of memory based approach which is used currently.

[ https://issues.apache.org/jira/browse/YARN-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687409#comment-13687409 ] Omkar Vinit Joshi commented on YARN-851: Thanks [~bikassaha] for identifying this.

[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-tabpanelfocusedCommentId=13687411#comment-13687411 ] Omkar Vinit Joshi commented on YARN-613: As a part of YARN-694

[jira] [Resolved] (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:all-tabpanel ] Omkar Vinit Joshi resolved YARN-613. Resolution: Fixed Fix Version/s: 2.1.0-beta Create NM proxy per NM instead of

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13687421#comment-13687421 ] Vinod Kumar Vavilapalli commented on YARN-791: -- bq. I suggested this on

[jira] [Commented] (YARN-845) RM crash with NPE on NODE_UPDATE

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

[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.13.patch change listApplications api to take in a list of application types

  1   2   >