You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2016/01/18 17:01:39 UTC
[jira] [Created] (YARN-4602) Message/notification service between
containers
Junping Du created YARN-4602:
--------------------------------
Summary: Message/notification service between containers
Key: YARN-4602
URL: https://issues.apache.org/jira/browse/YARN-4602
Project: Hadoop YARN
Issue Type: Sub-task
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)