You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2012/09/03 04:58:07 UTC
[jira] [Assigned] (CAMEL-5546) Zookeper master election logic is
too tightly bound to the route policy logic
[ https://issues.apache.org/jira/browse/CAMEL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-5546:
-----------------------------------
Assignee: Willem Jiang
> 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
> Assignee: Willem Jiang
> 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