You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2015/03/18 19:30:39 UTC

[jira] [Resolved] (MAPREDUCE-3536) consider whether the same instance of a ServiceStateChangeListener should be allowed to listen to events

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

Harsh J resolved MAPREDUCE-3536.
--------------------------------
    Resolution: Duplicate

> consider whether the same instance of a ServiceStateChangeListener should be allowed to listen to events
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3536
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3536
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0, 2.0.0-alpha
>            Reporter: Steve Loughran
>            Priority: Trivial
>
> Currently there is no limit on the number of times a listener can register for events; it's a simple list. A service must unregister the same number of times that it registers.
> Is this the desired behaviour? If so it should be documented in the {{Service}} interface rather than just implicitly in the {{AbstractService}} implementation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)