camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wheat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5546) Zookeper master election logic is too tightly bound to the route policy logic
Date Fri, 31 Aug 2012 11:00:07 GMT

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

Andrew Wheat updated CAMEL-5546:
--------------------------------

    Patch Info: Patch Available
    
> Zookeper master election logic is too tightly bound to the route policy logic
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-5546
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5546
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-zookeeper
>    Affects Versions: 2.10.0
>            Reporter: Andrew Wheat
>            Priority: Minor
>         Attachments: CAMEL-5546.diff
>
>
> The current structure of the ZooKeeperRoutePolicy does not allow the master election
to be re-used.
> Extracting the master election to a separate top-level class with a suitable, simple
API;
> {noformat}public boolean isMaster() { ... } {noformat}
> would make re-using the election for things that are not a route easier.
> The election constructor then takes the same parameters as the existing ZookeeperRoutePolicy,
and the new ZooKeeperRoutePolicy would take an election instance.

--
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