[jira] [Assigned] (YARN-3418) AM to be able to set/update web URL and IPC ports post-registration

2018-03-05 Thread Rohith Sharma K S (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohith Sharma K S reassigned YARN-3418:
---

Assignee: (was: Rohith Sharma K S)

> 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
>Priority: Major
>
> 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
(v7.6.3#76005)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Assigned] (YARN-3418) AM to be able to set/update web URL and IPC ports post-registration

2015-03-30 Thread Rohith (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohith reassigned YARN-3418:


Assignee: Rohith

 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)