[
https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713992#comment-13713992
]
Robert Joseph Evans commented on YARN-896:
------------------------------------------
I filed one new JIRA for updating tokens in the RM YARN-941.
I started to file a JIRA for the AM to be informed of the location of its
already running containers, but as I was writing it I realized that it will not
give us enough information to be able to reattach to the containers. The only
thing it will give us is enough info to be able to go shoot the containers.
Simply because there is no metadata about what port the container may be
listening on or anything like that. It seems to me that we would be better off
keeping a log, similar to the MR job history log, that has in it all the data
the AM needs to look for running containers. If others see a different need
for this API, I am still happy to file a JIRA for it.
I have not filed a JIRA for anti-affinity yet either. I seem to remember
another JIRA for something like this already, but I have not found it yet. I
figure we can add in a long lived process flag for the scheduler when we run
across a use case for it.
The other parts discussed here, either already have a JIRA associated with the
same functionality, or I think need a bit more discussion about exactly what we
want to do. Namely log aggregation/processing and Hadoop "package"
management/rolling upgrades of live applications.
If I missed something please let me know.
> Roll up for long lived YARN
> ---------------------------
>
> Key: YARN-896
> URL: https://issues.apache.org/jira/browse/YARN-896
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Robert Joseph Evans
>
> YARN is intended to be general purpose, but it is missing some features to be
> able to truly support long lived applications and long lived containers.
> This ticket is intended to
> # discuss what is needed to support long lived processes
> # track the resulting JIRA.
--
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
