hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4602) Scalable and Simple Message Service for YARN application
Date Thu, 03 Mar 2016 13:40:18 GMT

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

Junping Du updated YARN-4602:
-----------------------------
    Summary: Scalable and Simple Message Service for YARN application  (was: Message/notification
service between containers)

> Scalable and Simple Message Service for YARN application
> --------------------------------------------------------
>
>                 Key: YARN-4602
>                 URL: https://issues.apache.org/jira/browse/YARN-4602
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: applications, resourcemanager
>            Reporter: Junping Du
>            Assignee: Junping Du
>
> Currently, mostly communications among YARN daemons, services and applications are go
through RPC. In almost all cases, logic running inside of containers are RPC client but not
server because it get launched inflight. The only special case is AM container, because it
get launched earlier than any other containers so it can be RPC server and tell new coming
containers server address in application logic (like MR AM). 
> The side effects are: 
> 1. When AM container get failed, the new AM attempts will get launched with new address/port,
so previous RPC are broken.
> 2. Application's requirement are variable, there could be other dependency between containers
(not AM), so some container failed over will affect other containers' running logic.
> It is better to have some message/notification mechanism between containers for handle
above cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message