diff options
author | Kotresh HR <khiremat@redhat.com> | 2018-05-07 01:23:46 -0400 |
---|---|---|
committer | jiffin tony Thottan <jthottan@redhat.com> | 2018-06-11 10:18:03 +0000 |
commit | 0d744dbae27a3394bc449bf4489957e6f86f4891 (patch) | |
tree | cee0d79af474fc9340e88295bd81344e8b57cff0 /libgfdb.pc.in | |
parent | 978e85fcd53895cc4902ea0ab3cfcfacc1077315 (diff) |
geo-rep: Fix upgrade issue
Cause and Analysis:
The last synced changelog for entry operations is
marked in current version to avoid re-processing
of already processed entry operations in a batch
during crash/restart of geo-rep. This was not
present in previous versoins.
The marker is maintained in the dictionary with the
key 'last_synced_entry' and dictionary is persisted
into status file. So upgrading to current version in
which the marker is present was failing with KeyError.
Solution:
Load the dictionary with default keys first which
contains all the keys including latest ones and then
load the values from status file instead of doing
otherwise.
Backport of
> patch: https://review.gluster.org/19969/
> Change-Id: Ic654e6f9a3c97f616761f1362f890352a2186fb4
> Signed-off-by: Kotresh HR <khiremat@redhat.com>
(cherry picked from commit 23c1385b5f6f6103e820d15ecfe1df31940fdb45)
fixes: bz#1577862
Change-Id: Ic654e6f9a3c97f616761f1362f890352a2186fb4
Signed-off-by: Kotresh HR <khiremat@redhat.com>
Diffstat (limited to 'libgfdb.pc.in')
0 files changed, 0 insertions, 0 deletions