hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3995) Add support for static service lifecycle listeners .
Date Fri, 09 Mar 2012 17:58:58 GMT

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

Steve Loughran updated MAPREDUCE-3995:

    Attachment: MAPREDUCE-3995.patch

First pass for review -no tests. 

This is designed to be as simple as possible -the same service listener is used for the "global"
listeners, and the notifications are blocking on state changes. I started to write something
asynchronous but it was over-complex, hard to test and could easily leak threads. 

The global listener list is synchronised on the list itself, both for changes and for the
list run through itself. Listeners must not attempt to unregister themselves during a callback
or the iterator will fail.
> Add support for  static service lifecycle listeners .
> -----------------------------------------------------
>                 Key: MAPREDUCE-3995
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3995
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2
>    Affects Versions: 0.23.1, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: MAPREDUCE-3995.patch
> Add support to {{AbstractService}} that allow callers to register listeners for all instances.
The existing listener interface could be used. This allows management tools to hook into the
> The static listeners would be invoked for all state changes except creation (base class
shouldn't be handing out references to itself at this point).
> These static events could all be async, pushed through a shared {{ConcurrentLinkedQueue}};
failures logged at warn and the rest of the listeners invoked.

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


View raw message