You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Jian He (JIRA)" <ji...@apache.org> on 2017/09/13 17:34:01 UTC

[jira] [Resolved] (YARN-6067) Applications API Service HA

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

Jian He resolved YARN-6067.
---------------------------
    Resolution: Fixed

Because the api-server is stateless, users can achieve HA is by having a load balancer fronting multiple instances of api-server.
If we merge the api-server into RM to achieve HA, then this is a dup of YARN-6626.

> Applications API Service HA
> ---------------------------
>
>                 Key: YARN-6067
>                 URL: https://issues.apache.org/jira/browse/YARN-6067
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Gour Saha
>
> We need to start thinking about HA for the Applications API Service. How do we achieve it? Should API Service become part of the RM process to get a lot of things for free? Should there be some other strategy. We need to start the discussion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org