[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-tabpanelfocusedCommentId=13647425#comment-13647425 ] Hudson commented on YARN-618: - Integrated in Hadoop-Yarn-trunk #201 (See

[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-tabpanelfocusedCommentId=13647489#comment-13647489 ] Hudson commented on YARN-618: - Integrated in Hadoop-Hdfs-trunk #1390 (See

[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-tabpanelfocusedCommentId=13647544#comment-13647544 ] Hudson commented on YARN-618: - Integrated in Hadoop-Mapreduce-trunk #1417 (See

[jira] [Commented] (YARN-621) RM triggers web auth failure before first job

[ https://issues.apache.org/jira/browse/YARN-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647687#comment-13647687 ] Allen Wittenauer commented on YARN-621: --- Some more details: * With the exception of

[jira] [Updated] (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:all-tabpanel ] Chris Riccomini updated YARN-614: - Attachment: YARN-614-1.patch Retry attempts automatically for hardware failures or YARN

[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-tabpanelfocusedCommentId=13647750#comment-13647750 ] Chris Riccomini commented on YARN-614: -- Added a new patch. Resolves 1 (switch

[jira] [Commented] (YARN-636) Restore clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647769#comment-13647769 ] Bikas Saha commented on YARN-636: - If this is being fully covered in YARN-582 then please

[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-tabpanelfocusedCommentId=13647770#comment-13647770 ] Chris Riccomini commented on YARN-614: -- Hey Bikas, Looking into the recovery stuff a

[jira] [Assigned] (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 ] Chris Nauroth reassigned YARN-641: -- Assignee: Chris Nauroth (was: Zhijie Shen) Make AMLauncher in RM Use NMClient

[jira] [Assigned] (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 ] Chris Nauroth reassigned YARN-641: -- Assignee: Zhijie Shen (was: Chris Nauroth) Accidentally assigned this to myself. Giving it

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13647914#comment-13647914 ] Jian He commented on YARN-638: -- Simply adding RMDelegationTokens back to

[jira] [Updated] (YARN-638) Restore RMDelegationTokens 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: - Summary: Restore RMDelegationTokens after RM Restart (was: Add RMDelegationTokens back to

[jira] [Updated] (YARN-581) Test and verify that app delegation tokens are added to tokenNewer after RM restart

[ https://issues.apache.org/jira/browse/YARN-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-581: - Summary: Test and verify that app delegation tokens are added to tokenNewer after RM restart (was: Test and

[jira] [Commented] (YARN-581) Test and verify that app delegation tokens are added to tokenNewer after RM restart

[ https://issues.apache.org/jira/browse/YARN-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647927#comment-13647927 ] Jian He commented on YARN-581: -- changed the title, this patch handles restoring

[jira] [Commented] (YARN-636) Restore clientToken for app attempt after RM restart

[ https://issues.apache.org/jira/browse/YARN-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647941#comment-13647941 ] Jian He commented on YARN-636: -- Currently, this is not covered in YARN-582, I separated the

[jira] [Updated] (YARN-581) Test and verify that app delegation tokens are added to tokenRenewer after RM restart

[ https://issues.apache.org/jira/browse/YARN-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-581: - Summary: Test and verify that app delegation tokens are added to tokenRenewer after RM restart (was: Test

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

[ https://issues.apache.org/jira/browse/YARN-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-629: --- Attachment: YARN-629.3.patch Make YarnRemoteException not be rooted at IOException

[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-tabpanelfocusedCommentId=13648021#comment-13648021 ] Xuan Gong commented on YARN-629: Drop test code to verify NMNotYetReadyException and

[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-tabpanelfocusedCommentId=13648022#comment-13648022 ] Xuan Gong commented on YARN-629: Uploaded new patch to do all the MR change at

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: YARN-326-2.patch Add multi-resource scheduling to the fair scheduler

[jira] [Updated] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-326: Attachment: (was: YARN-326-2.patch) Add multi-resource scheduling to the fair scheduler

[jira] [Commented] (YARN-326) Add multi-resource scheduling to the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648025#comment-13648025 ] Sandy Ryza commented on YARN-326: - Uploaded a patch that fixes a couple bugs, includes more

[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-tabpanelfocusedCommentId=13648037#comment-13648037 ] Bikas Saha commented on YARN-582: - Is the null check necessary? the underlying protobuf

[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-tabpanelfocusedCommentId=13648040#comment-13648040 ] Bikas Saha commented on YARN-582: - Also, we could be better off storing credentials in

[jira] [Created] (YARN-642) Fix up RMWebServices#getNodes

Sandy Ryza created YARN-642: --- Summary: Fix up RMWebServices#getNodes Key: YARN-642 URL: https://issues.apache.org/jira/browse/YARN-642 Project: Hadoop YARN Issue Type: Bug Components:

[jira] [Created] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

Jian He created YARN-643: Summary: WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition Key: YARN-643 URL:

[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-tabpanelfocusedCommentId=13648075#comment-13648075 ] Bikas Saha commented on YARN-513: - This will not work since for different protocols we

[jira] [Updated] (YARN-642) Fix up RMWebServices#getNodes

[ https://issues.apache.org/jira/browse/YARN-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-642: Labels: incompatible (was: ) Fix up RMWebServices#getNodes -

[jira] [Created] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

Omkar Vinit Joshi created YARN-644: -- Summary: Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer Key: YARN-644 URL:

[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.20130502.patch Updating existing test cases. In

[jira] [Created] (YARN-645) Move RMDelegationTokenSecretManager from yarn-server-common to yarn-server-resourcemanager

Jian He created YARN-645: Summary: Move RMDelegationTokenSecretManager from yarn-server-common to yarn-server-resourcemanager Key: YARN-645 URL: https://issues.apache.org/jira/browse/YARN-645 Project: Hadoop

[jira] [Updated] (YARN-645) Move RMDelegationTokenSecretManager from yarn-server-common to yarn-server-resourcemanager

[ https://issues.apache.org/jira/browse/YARN-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-645: - Attachment: YARN-645.patch this patch moved RMDelegationTokenSecretManager Move

[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-tabpanelfocusedCommentId=13648197#comment-13648197 ] Bikas Saha commented on YARN-614: - Unfortunately that is not how it happens. The RECOVER

[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-tabpanelfocusedCommentId=13648204#comment-13648204 ] Vinod Kumar Vavilapalli commented on YARN-513: -- While Bikas continues to review

[jira] [Updated] (YARN-645) Move RMDelegationTokenSecretManager from yarn-server-common to yarn-server-resourcemanager

[ https://issues.apache.org/jira/browse/YARN-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-645: - Attachment: YARN-645.1.patch Move RMDelegationTokenSecretManager from yarn-server-common to