[
https://issues.apache.org/jira/browse/YARN-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707196#comment-13707196
]
Vinod Kumar Vavilapalli commented on YARN-701:
----------------------------------------------
Tx for the review and test, Omkar!
bq. It makes sense to remove appAttemptId from request.. thoughts?? backward
compatibility?
We should do this, but i'll file a separate ticket to keep focus.
bq. However there is a problem if we restart node manager on which AM was
running during application run. Attaching logs.
Checked the logs. It's an existing bug where MR AM doesn't go away when told
to. Will file a ticket.
> ApplicationTokens should be used irrespective of kerberos
> ---------------------------------------------------------
>
> Key: YARN-701
> URL: https://issues.apache.org/jira/browse/YARN-701
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.1.0-beta
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Priority: Blocker
> Attachments: YARN-701-20130520.txt, YARN-701-20130709.3.txt,
> YARN-701-20130710.txt, YARN-701-20130712.txt,
> yarn-ojoshi-resourcemanager-HW10351.local.log
>
>
> - Single code path for secure and non-secure cases is useful for testing,
> coverage.
> - Having this in non-secure mode will help us avoid accidental bugs in AMs
> DDos'ing and bringing down RM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
