[
https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764356#comment-13764356
]
Hudson commented on YARN-1098:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1545 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1545/])
YARN-1098. Separate out RM services into Always On and Active (Karthik Kambatla
via bikas) (bikas:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1521560)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ResourceManager.java
> Separate out RM services into "Always On" and "Active"
> ------------------------------------------------------
>
> 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
> Fix For: 2.3.0
>
> Attachments: yarn-1098-1.patch, yarn-1098-2.patch, yarn-1098-3.patch,
> yarn-1098-4.patch, yarn-1098-5.patch, 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
