[
https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-1098:
-----------------------------------
Description:
>From discussion on YARN-1027, it makes sense to separate out services that are
>stateful and stateless. The stateless services can run perennially
>irrespective of whether the RM is in Active/Standby state, while the stateful
>services need to be started on transitionToActive() and completely shutdown
>on transitionToStandby().
The external-facing stateless services should respond to the client/AM/NM
requests depending on whether the RM is Active/Standby.
was:
>From discussion on YARN-1027, it makes sense to separate out services that are
>stateful and stateless. The stateless services can be HA-agnostic and be run
>perennially irrespective of whether the RM is in Active/Standby state, while
>the stateful services need to be aware of HA and be started on
>transitionToActive() and completely shutdown on transitionToStandby().
> Separate out stateless services from stateful services in the RM
> ----------------------------------------------------------------
>
> Key: YARN-1098
> URL: https://issues.apache.org/jira/browse/YARN-1098
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Labels: ha
> Attachments: yarn-1098-approach.patch, yarn-1098-approach.patch
>
>
> From discussion on YARN-1027, it makes sense to separate out services that
> are stateful and stateless. The stateless services can run perennially
> irrespective of whether the RM is in Active/Standby state, while the stateful
> services need to be started on transitionToActive() and completely shutdown
> on transitionToStandby().
> The external-facing stateless services should respond to the client/AM/NM
> requests depending on whether the RM is Active/Standby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
