[
https://issues.apache.org/jira/browse/YARN-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809610#comment-13809610
]
Omkar Vinit Joshi commented on YARN-1359:
-----------------------------------------
Today node manager doesn't do this filtering of tokens.
Proposal :-
Let node manager filter out AMRMToken from tokens while launching container
other than AM. Thereby we are only (truly) allowing AM container to talk to RM
on AMRM protocol.
Enhancements :- today node manager doesn't know which container is AM
container. There are lot of problems because of this. So we first need a way to
inform node manager about the container being AM. As today node manager comes
to know everything about the new container from container token so it will be
better to add isAM flag inside the token . Thoughts?
(Note: we are anyway not encouraging users to talk to RM using multiple
containers which are sharing same AMRMToken).
> AMRMToken should not be sent to Container other than AM.
> --------------------------------------------------------
>
> Key: YARN-1359
> URL: https://issues.apache.org/jira/browse/YARN-1359
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Omkar Vinit Joshi
> Assignee: Omkar Vinit Joshi
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
