tree 32e9dd055e1b8280f59c75da0c6b499e1879c55e
parent c46a4b537610fb1205fe7e415940d0c4db31ce91
author Jack Vanlightly <vanlightly@gmail.com> 1615533631 -0800
committer Enrico Olivelli <eolivelli@apache.org> 1615533650 +0100

Add fencing to recovery reads to avoid data loss issue

Descriptions of the changes in this PR:

### Motivation

Adding the fencing flag to recovery reads avoids a data loss scenario as described in [issue 2614](https://github.com/apache/bookkeeper/issues/2614)

### Changes

Added the fencing flag to recovery reads. Refactored some mocking unit test code to introduce fencing and allow two writers to share the same bookie state. Added a new unit to verify the fix. You can recreate the initial problem by removing the fencing flag from recovery reads and running the new unit test.

Master Issue: #2614

Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Andrey Yegorov <andrey.yegorov@datastax.com>

This closes #2616 from Vanlightly/fix-fencing

(cherry picked from commit 017307bc67431a7616861ad09927c4e3327633d1)
Signed-off-by: Enrico Olivelli <eolivelli@apache.org>