hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1098) Separate out RM services into "Always On" and "Active"
Date Wed, 04 Sep 2013 20:40:53 GMT

    [ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758308#comment-13758308
] 

Bikas Saha commented on YARN-1098:
----------------------------------

Not a big fan of anonymous classes. We should probably create an ActiveServices that extends
CompositeService. We can later add transitionToActive() and transitionToStandby() method to
this object.

Dispatcher can actually also go into ActiveServices for now. We can move it into the main
service later on because it looks like that the HAProtocol service will be the only always
on service to start with.

Jenkins is not happy with the patch.


                
> 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
>         Attachments: yarn-1098-1.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

Mime
View raw message