tree 75aeb918eabf36d140584e12fc1dc7d2f59a236d
parent bbb0113d61d3c4c47079f5924ad00bc433925b63
author karanmehta93 <k.mehta@salesforce.com> 1604397945 -0800
committer GitHub <noreply@github.com> 1604397945 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfoSt5CRBK7hj4Ov3rIwAAdHIIAKAKluSpGG8AhOiTTeksaF90
 8O/Eh5tDcbVzksW26Sq0w7/R0vLy9+cI27bEHfNHJhJUMOVTdd9WBG4S9hTSGjoW
 lFEXtBhbOnsYmUgOMsimWoPN8yIXvgqKxUBn+FeKWus/mSAvrWImVbyNV3PjhHYG
 JjtRX4uWJ4g7hOY5pRRGi18qQ35rveo2ldN1SvWzJMZopTxBYVahobPxI3KdWi0g
 trEzqR49QXjXUMwZeg2DqUI7SnFPVJdMR9gIzC2EsBaHw45Oug6+huFQZzxLPF3A
 oZKkbCDQUNki/+iqOO8yJ+UZq/s1okIfdg2qhXE1cSNcDc3cebxa7HpPoV8IKvc=
 =fUBj
 -----END PGP SIGNATURE-----
 

ZookeeperClient should retry instantly on zk session expiry (#2450)

Descriptions of the changes in this PR:

### Motivation

Currently, we wait for `sessionTimeoutMs` before initiating a new zk cnxn. Session expiry is recevied only
when zk quprum is in a healthy state and can acquire a quorum to expire a session.
All other connection loss retries happen at zk client library transparently.

There is not much benefit waiting at BK client level.

### Changes

Updated the values for backoff and maxbackoff to 0 seconds.



* ZookeeperClient should retry instantly on zk session expiry

Currently, we wait for `sessionTimeoutMs` before initiating a new zk cnxn. Session expiry is recevied only
when zk quprum is in a healthy state and can acquire a quorum to expire a session.
All other connection loss retries happen at zk client library transparently.

* Added comments