hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3970) Add ServiceOperations class to aid working with Services
Date Thu, 15 Mar 2012 10:39:38 GMT

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

Steve Loughran commented on MAPREDUCE-3970:
-------------------------------------------

-committing; new methods implicitly have no backwards compatibility issues, only change to
{{AbstractService}} is to move the sttaic state check method over for earlier invocation on
state change operations.
                
> Add ServiceOperations class to aid working with Services
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-3970
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3970
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2
>    Affects Versions: 0.23.1, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: MAPREDUCE-3970.patch, MAPREDUCE-3970.patch
>
>
> Add Helper methods to move things through lifecycles. init->start is common, stop-if-service!=null
another. Some static methods can execute these, and even call stop() if init() raises an exception.
These could go into a class ServiceOps in the same package. These can be used by those services
that wrap other services, and help manage more robust shutdowns.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message