[jira] [Updated] (YARN-571) User should not be part of ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-571: --- Attachment: YARN-571.20130522.2.patch We are removing user from containerLaunchContext as it

[jira] [Commented] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668505#comment-13668505 ] Omkar Vinit Joshi commented on YARN-578: Thanks [~sandyr] for reviewing.. Fixed all

[jira] [Updated] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-578: --- Attachment: YARN-578-20130528.patch NodeManager should use SecureIOUtils for serving and

[jira] [Commented] (YARN-714) AMRM protocol changes for sending NMToken list

[ https://issues.apache.org/jira/browse/YARN-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668695#comment-13668695 ] Omkar Vinit Joshi commented on YARN-714: updating patch with protocol changes with

[jira] [Updated] (YARN-714) AMRM protocol changes for sending NMToken list

[ https://issues.apache.org/jira/browse/YARN-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-714: --- Attachment: YARN-714-20130528.patch AMRM protocol changes for sending NMToken list

[jira] [Commented] (YARN-714) AMRM protocol changes for sending NMToken list

[ https://issues.apache.org/jira/browse/YARN-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668744#comment-13668744 ] Omkar Vinit Joshi commented on YARN-714: Fixing findbug warnings and javadoc

[jira] [Updated] (YARN-714) AMRM protocol changes for sending NMToken list

[ https://issues.apache.org/jira/browse/YARN-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-714: --- Attachment: YARN-714-20130528.1.patch AMRM protocol changes for sending NMToken list

[jira] [Commented] (YARN-435) Make it easier to access cluster topology information in an AM

[ https://issues.apache.org/jira/browse/YARN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669570#comment-13669570 ] Omkar Vinit Joshi commented on YARN-435: After discussion with [~vinodkv]

[jira] [Updated] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-578: --- Attachment: YARN-578-20130529.patch NodeManager should use SecureIOUtils for serving and

[jira] [Assigned] (YARN-552) Expose resource metrics as part of YarnClusterMetrics

[ https://issues.apache.org/jira/browse/YARN-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-552: -- Assignee: Omkar Vinit Joshi Expose resource metrics as part of YarnClusterMetrics

[jira] [Commented] (YARN-578) NodeManager should use SecureIOUtils for serving and aggregating logs

[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669891#comment-13669891 ] Omkar Vinit Joshi commented on YARN-578: The patch is same for both branch-2 and

[jira] [Commented] (YARN-692) Creating AMNMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670997#comment-13670997 ] Omkar Vinit Joshi commented on YARN-692: As a part of this patch only enabling

[jira] [Commented] (YARN-733) TestNMClient fails occasionally

[ https://issues.apache.org/jira/browse/YARN-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671054#comment-13671054 ] Omkar Vinit Joshi commented on YARN-733: Yes this is occasionally failing for me too

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Description: This is related to YARN-613 . Here we will be implementing NMToken generation on

[jira] [Updated] (YARN-693) Sending NMToken to AM on allocate call if container is allocated for the first time on underlying NM for given AM

[ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-693: --- Description: This is part of YARN-613. Here AM will receive NMToken in allocate call only if *

[jira] [Updated] (YARN-692) Creating AMNMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692.20130530.1.patch Creating AMNMToken master key on RM and sharing it

[jira] [Created] (YARN-738) TestClientRMTokens is failing irregularly while running all yarn tests

Omkar Vinit Joshi created YARN-738: -- Summary: TestClientRMTokens is failing irregularly while running all yarn tests Key: YARN-738 URL: https://issues.apache.org/jira/browse/YARN-738 Project: Hadoop

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692.20130530.2.patch Fixing findbug and release warnings..

[jira] [Commented] (YARN-733) TestNMClient fails occasionally

[ https://issues.apache.org/jira/browse/YARN-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671712#comment-13671712 ] Omkar Vinit Joshi commented on YARN-733: [~zjshen] small nit bq. may still need

[jira] [Commented] (YARN-694) AM uses the AMNMToken to authenticate all communication with NM. NM remembers and updates token across RM restart

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671819#comment-13671819 ] Omkar Vinit Joshi commented on YARN-694: Need to fix NodeId check as a part of this

[jira] [Updated] (YARN-694) AM uses the NMToken to authenticate all communication with NM. NM remembers and updates token across RM restart

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Summary: AM uses the NMToken to authenticate all communication with NM. NM remembers and

[jira] [Updated] (YARN-694) AM uses the NMToken to authenticate all communication with NM. NM remembers and updates token across RM restart

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-694: --- Description: AM uses the NMToken to authenticate all the AM-NM communication. NM will validate

[jira] [Commented] (YARN-762) Javadoc params not matching in ContainerManagerImpl.authorizeRequest method

[ https://issues.apache.org/jira/browse/YARN-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13674575#comment-13674575 ] Omkar Vinit Joshi commented on YARN-762: [~niranjanmaisnam] thanks niranjan...

[jira] [Commented] (YARN-775) stream jobs are not cleaning the Yarn local-dirs after container is released

[ https://issues.apache.org/jira/browse/YARN-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677641#comment-13677641 ] Omkar Vinit Joshi commented on YARN-775: No you don't need to explicitly set it to

[jira] [Created] (YARN-785) Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replace with single API.

Omkar Vinit Joshi created YARN-785: -- Summary: Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replace with single API. Key: YARN-785

[jira] [Updated] (YARN-785) Every startContainer request send a set of information (auxiliary service related information) which is redundant. Can be replaced with single NodeManager API.

[ https://issues.apache.org/jira/browse/YARN-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-785: --- Summary: Every startContainer request send a set of information (auxiliary service related

[jira] [Created] (YARN-797) Remove KIND field from ContainerTokenIdentifier as it is not useful.

Omkar Vinit Joshi created YARN-797: -- Summary: Remove KIND field from ContainerTokenIdentifier as it is not useful. Key: YARN-797 URL: https://issues.apache.org/jira/browse/YARN-797 Project: Hadoop

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692-20130611.patch Creating NMToken master key on RM and sharing it with

[jira] [Updated] (YARN-797) DecodeIdentifier is broken. It was using KIND field for reflection and now we don't have class named as KIND.

[ https://issues.apache.org/jira/browse/YARN-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-797: --- Summary: DecodeIdentifier is broken. It was using KIND field for reflection and now we don't

[jira] [Updated] (YARN-797) DecodeIdentifier is broken. It was using KIND field for reflection and now we don't have class named as KIND.

[ https://issues.apache.org/jira/browse/YARN-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-797: --- Description: We need to fix the reflection code in Token.decodeIdentifier was: We need to

[jira] [Updated] (YARN-797) DecodeIdentifier is broken. It was using KIND field for reflection and now we don't have class named as KIND.

[ https://issues.apache.org/jira/browse/YARN-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-797: --- Description: We need to fix the reflection code in Token.decodeIdentifier. was: As we

[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: --- Description: This is part of YARN-613. As per the updated design, AM will receive per NM,

[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-20130610.patch Sending NMToken to AM on allocate call

[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: --- Description: This is part of YARN-613. As per the updated design, AM will receive per NM,

[jira] [Commented] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682458#comment-13682458 ] Omkar Vinit Joshi commented on YARN-692: rebasing after YARN-117

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692-20130613.patch Creating NMToken master key on RM and sharing it with

[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-20130613.patch rebasing patch after YARN-117 Sending

[jira] [Commented] (YARN-694) AM uses the NMToken to authenticate all communication with NM. NM remembers and updates token across RM restart

[ https://issues.apache.org/jira/browse/YARN-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682793#comment-13682793 ] Omkar Vinit Joshi commented on YARN-694: Addressing below issues in this patch. *

[jira] [Updated] (YARN-694) AM uses the NMToken to authenticate all communication with NM. NM remembers and updates token across RM restart

[ 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-20130613.patch AM uses the NMToken to authenticate all communication

[jira] [Updated] (YARN-692) Creating NMToken master key on RM and sharing it with NM as a part of RM-NM heartbeat.

[ https://issues.apache.org/jira/browse/YARN-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-692: --- Attachment: YARN-692-20130613.1.patch reducing timeout to 180K. Creating

[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=13682914#comment-13682914 ] Omkar Vinit Joshi commented on YARN-639: [~zjshen] looked at your patch... minor

[jira] [Assigned] (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:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-610: -- Assignee: Omkar Vinit Joshi (was: Vinod Kumar Vavilapalli) ClientToken should not

[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=13683611#comment-13683611 ] Omkar Vinit Joshi commented on YARN-610: Here we will be making sure that AM has the

[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=13683625#comment-13683625 ] Omkar Vinit Joshi commented on YARN-610: also we can't send it via credentials as a

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

Omkar Vinit Joshi created YARN-822: -- Summary: Rename ApplicationToken to AMRMToken Key: YARN-822 URL: https://issues.apache.org/jira/browse/YARN-822 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130614.patch ClientToken should not be set in the environment

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

[ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684041#comment-13684041 ] Omkar Vinit Joshi commented on YARN-693: bq. NMToken should be in

[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-20130614.1.patch Sending NMToken to AM on allocate call

[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

[ https://issues.apache.org/jira/browse/YARN-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13684532#comment-13684532 ] Omkar Vinit Joshi commented on YARN-693: Fixed TestCases and find bug warnings..

[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] [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] [Resolved] (YARN-835) The name 'ApplicationTokenIdentifier' is misleading

[ https://issues.apache.org/jira/browse/YARN-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-835. Resolution: Duplicate The name 'ApplicationTokenIdentifier' is misleading

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

[ https://issues.apache.org/jira/browse/YARN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-822: --- Issue Type: Sub-task (was: Bug) Parent: YARN-386 Rename ApplicationToken to

[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=13685005#comment-13685005 ] Omkar Vinit Joshi commented on YARN-610: bq. Seems like the patch has gone stale,

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130616.patch ClientToken should not be set in the environment

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130616.3.patch ClientToken (ClientToAMToken) should not be set in

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

[ https://issues.apache.org/jira/browse/YARN-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-822: --- Attachment: YARN-822-20130617.patch Renaming TokenIdentifier, TokenSelector and SecretManager.

[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=13685801#comment-13685801 ] Omkar Vinit Joshi commented on YARN-610: updating the patch ..

[jira] [Created] (YARN-843) TestPipeApplication should not be using AMRMToken.

Omkar Vinit Joshi created YARN-843: -- Summary: TestPipeApplication should not be using AMRMToken. Key: YARN-843 URL: https://issues.apache.org/jira/browse/YARN-843 Project: Hadoop YARN Issue

[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=13685806#comment-13685806 ] Omkar Vinit Joshi commented on YARN-822: yes I will... YARN-843

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130617.patch ClientToken (ClientToAMToken) should not be set in

[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-20130617.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=13685913#comment-13685913 ] Omkar Vinit Joshi commented on YARN-694: Things pending.. * Fix

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130617.1.patch ClientToken (ClientToAMToken) should not be set in

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-610: --- Attachment: YARN-610-20130617.2.patch ClientToken (ClientToAMToken) should not be set in

[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-20130617.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: YARN-694-20130617.2.patch updating patch after YARN-610 Start

[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] [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] [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-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] [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] [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] [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 to

[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] [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] [Assigned] (YARN-797) DecodeIdentifier is broken. It was using KIND field for reflection and now we don't have class named as KIND.

[ https://issues.apache.org/jira/browse/YARN-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-797: -- Assignee: Omkar Vinit Joshi DecodeIdentifier is broken. It was using KIND field for

[jira] [Resolved] (YARN-797) DecodeIdentifier is broken. It was using KIND field for reflection and now we don't have class named as KIND.

[ https://issues.apache.org/jira/browse/YARN-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-797. Resolution: Invalid DecodeIdentifier is broken. It was using KIND field for reflection

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130618.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.patch App submission fails on secure deploy

[jira] [Commented] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13688588#comment-13688588 ] Omkar Vinit Joshi commented on YARN-854: Fixing one more thing.. making sure

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.1.patch App submission fails on secure deploy

[jira] [Updated] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-854: --- Attachment: YARN-854.20130619.2.patch App submission fails on secure deploy

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130619.patch Share NMTokens using NMTokenCache (api-based) instead

[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=13688812#comment-13688812 ] Omkar Vinit Joshi commented on YARN-851: Fixed above comments. removed

[jira] [Commented] (YARN-862) ResourceManager and NodeManager versions should match on node registration or error out

[ https://issues.apache.org/jira/browse/YARN-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689496#comment-13689496 ] Omkar Vinit Joshi commented on YARN-862: Won't this become a problem in case we are

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130619.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130620.patch Share NMTokens using NMTokenCache (api-based) instead

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: (was: YARN-851-20130620.patch) Share NMTokens using NMTokenCache

[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=13689792#comment-13689792 ] Omkar Vinit Joshi commented on YARN-851: fixing vinod's comments. marking class and

[jira] [Updated] (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:all-tabpanel ] Omkar Vinit Joshi updated YARN-851: --- Attachment: YARN-851-20130620.1.patch Share NMTokens using NMTokenCache (api-based)

  1   2   3   4   5   6   7   8   >