geo-rep / gsyncd: play nicely with peer multiplexing when setting a checkpoint

From upstream commit 01217e4e16677b13c7febc66e4e4ca3f0025739b:
> The gsyncd invocation that instruments the "geo-rep config" command is
> multiplexed over peers to ensure the uniformity of configuration.
> In general, that works well, but checkpoint setting is a special case,
> because (unlike other instances of config-set) it is logged (as recording
> of checkpoint events is part of the feature).
>
> Problem is that the path components leading to the log file are
> created only on the original node, where gsyncd was started.
> Therefore the logging attempt will fail on the other nodes.
>
> Fix: ignore if opening the logfile on behalf of checkpoint setting
> fails with ENOENT.
>
> Change-Id: I677f3f081bf4b9e3ba4d25d58979d86931e6beb4
> BUG: 881997
> Signed-off-by: Csaba Henk <csaba@redhat.com>
> Reviewed-on: http://review.gluster.org/4248
> Reviewed-by: Niels de Vos <ndevos@redhat.com>
> Tested-by: Christos Triantafyllidis <ctrianta@redhat.com>
> Reviewed-by: Christos Triantafyllidis <ctrianta@redhat.com>
> Reviewed-by: Anand Avati <avati@redhat.com>

Change-Id: I83b2cb7f78cf8613b78d3c8ff8e7b3828050cfc3
BUG: 881736
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Reviewed-on: https://code.engineering.redhat.com/gerrit/1929
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Tested-by: Vijay Bellur <vbellur@redhat.com>

0 files changed, 0 insertions, 0 deletions