tree a381d8d1adfe11df16d7d370c376b1294238a365
parent 4d4465031012a126afcc78dcd3041829fee173d9
author karanmehta93 <k.mehta@salesforce.com> 1604301802 -0800
committer GitHub <noreply@github.com> 1604301802 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfn7PqCRBK7hj4Ov3rIwAAdHIIALCe4cNi/QSAwb6BT0sSN7aZ
 bdgp1yE/TC45/6mEOBJmCmXCaKPvkfUCJ4yQ2OluKgI8mz6N4hArSMlWBlLrjX7y
 KesV360vH5lRoF9lt8rEsYehKyJ5p5KCCR0lVH+FsJaR6i4L61gM7eHnHVvMfy5b
 WYZJCd+B6r64QkJxPguXwLkfxdYprelwh6OyBs/8KD2LTf1U6br9p1k0Qu06F3WM
 yPQ/SlKzr0gkHyuoEpp9kv7zmQB4vHnu8wntmt6DG6fWiup8ueMYuhA5Zc26DkYh
 A7ZfkWqmso4zbrXE8ZR5e4vN5/WNpjo9QapuJdMz5KWu8bG/MXvfc7UcQA6qyNQ=
 =kyKI
 -----END PGP SIGNATURE-----
 

Autorecovery may hang indefinitely when zookeeper connection blips

Descriptions of the changes in this PR:

### Motivation

In certain circumstances, all AR processes were running but not performing any replication. Thus ledgers remain under-replicated for periods more than the threshold defined by our monitoring system. The reason is that the latch here gets countdown only under certain condition.

### Changes

Ensure that countdown latch is released for any ZK event. Also log the zk event.

Master Issue: #2302 

Reviewers: Enrico Olivelli <eolivelli@apache.org>, Anup Ghatage <gathage@apache.org>

This closes #2471 from karanmehta93/ar-zk-bug