[
https://issues.apache.org/jira/browse/YARN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390006#comment-14390006
]
Rohith commented on YARN-3418:
------------------------------
Thinking instead of supporting new AM-RM IPC call,
{{ApplicationMasterProtocol.registerApplicationMaster}} can be reused.
Currently, on registration RM throws InvalidApplicationMasterRequestException.
As a supporting updating web/rpc/trackingUrl , an update event to
RMAppAttemptImpl can be send. But AM has to take descision whether to exit or
continue running.
> AM to be able to set/update web URL and IPC ports post-registration
> -------------------------------------------------------------------
>
> Key: YARN-3418
> URL: https://issues.apache.org/jira/browse/YARN-3418
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Rohith
>
> Currently the AM can only set the IPC and HTTP(s) ports on AM registration.
> This
> # creates a possible race condition: the IPC and HTTP ports need to come up
> before the app is fully initialised. This is particularly true on
> work-preserving AM restarts, as the AM will depend on the list of containers
> supplied during registration to build its internal state.
> # prevents the AM from changing these values dynamically during application
> execution. This matters if the Web or IPC services are hosted not in the AM,
> but in a deployed container. If the container is restarted, there's no way to
> rebind the services.
> A new AM-RM IPC call to publish updated binding information is needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
