[
https://issues.apache.org/jira/browse/ZOOKEEPER-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qihong Xu updated ZOOKEEPER-2927:
---------------------------------
Description:
When zookeeper quorum recovers from shutdown/crash, a client with a local
session will reconnect to a random server in quorum. If this random-chosen
server is not leader and does not own the local session previously, it will
forward this session to leader for validation. And then if this is a global
session, leader will update its owner, if not, leader adds Boolean false to
packet and does nothing.
Since our system involves mostly local session and has a large amount of
connections, this procedure may be redundant and add potential pressure to
leader. Is this reasonable for the reconnect scenario that local session
validation not forward to leader, instead return by follower directly?
was:
When zookeeper quorum recovers from shutdown/crash, a client with a local
session will reconnect to a random server in quorum. If this random-chosen
server is not leader and does not own the local session previously, it will
forward this session to leader for validation. And then if this is a global
session, leader will update its owner, if not, leader adds Boolean false to
packet and does nothing.
Since our system involves mostly local session and has a large amount of
connections, this procedure may be redundant and add potential pressure to
leader. Is this reasonable for the reconnect scenario that local session does
not forward to leader, instead return by follower directly?
> Local session reconnect validation not forward to leader
> --------------------------------------------------------
>
> Key: ZOOKEEPER-2927
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2927
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client, quorum, server
> Affects Versions: 3.5.3
> Environment: configuration management system based on zookeeper 3.5.3
> Reporter: Qihong Xu
> Priority: Minor
>
> When zookeeper quorum recovers from shutdown/crash, a client with a local
> session will reconnect to a random server in quorum. If this random-chosen
> server is not leader and does not own the local session previously, it will
> forward this session to leader for validation. And then if this is a global
> session, leader will update its owner, if not, leader adds Boolean false to
> packet and does nothing.
> Since our system involves mostly local session and has a large amount of
> connections, this procedure may be redundant and add potential pressure to
> leader. Is this reasonable for the reconnect scenario that local session
> validation not forward to leader, instead return by follower directly?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
