[
https://issues.apache.org/jira/browse/CAMEL-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leo Wang updated CAMEL-8208:
----------------------------
Description:
My company is using ZooKeeperRoutePolicy to maintain a Master/Slaver cluster.
Sometimes the cluster got network problem which make the app server disconnect
from remote ZooKeeper server. The disconnection usually don't last long but
still long enough to expire the zookeeper session of ZooKeeperRoutePolicy. By
our observation, it seems ZooKeeperRoutePolicy would not recovery and do
re-election after session expiration which lead to multiple master situation.
Is it possible to do enhancement or bug fixing on this?
was:
My company is using ZooKeeperRoutePolicy to maintain a Master/Slaver cluster.
Sometimes the cluster got network problem which make the app server disconnect
from remote ZooKeeper server. The disconnection usually don't last long but
still long enough to expire the zookeeper session of ZooKeeperRoutePolicy. By
our observation, it seems ZooKeeperRoutePolicy would not recovery and do
re-election after session expiration which lead to multiple master situation.
Is it possible to do imhencement or bug fixing on this?
> ZooKeeperRoutePolicy is not able to recover after session expiration
> --------------------------------------------------------------------
>
> Key: CAMEL-8208
> URL: https://issues.apache.org/jira/browse/CAMEL-8208
> Project: Camel
> Issue Type: Bug
> Components: camel-zookeeper
> Affects Versions: 2.13.2
> Reporter: Leo Wang
>
> My company is using ZooKeeperRoutePolicy to maintain a Master/Slaver cluster.
> Sometimes the cluster got network problem which make the app server
> disconnect from remote ZooKeeper server. The disconnection usually don't last
> long but still long enough to expire the zookeeper session of
> ZooKeeperRoutePolicy. By our observation, it seems ZooKeeperRoutePolicy would
> not recovery and do re-election after session expiration which lead to
> multiple master situation.
> Is it possible to do enhancement or bug fixing on this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
