summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorSaravanakumar Arumugam <sarumuga@redhat.com>2016-06-29 15:36:06 +0530
committerJeff Darcy <jdarcy@redhat.com>2016-07-11 15:50:13 -0700
commitf938b3a26ffab9482d5f910ee76d2bb2b370517f (patch)
treec5b8f275bfe3c405e5ed665505c80b81183f1d99 /ChangeLog
parentbfbadab0d65f38d2719ceb4d5c9144377db9d4d5 (diff)
glusterd/geo-rep: Handle empty monitor.status during upgrade
Problem: Consider geo-replication is in Stopped state. Following which, glusterfs is upgraded (where monitor.status is the new status file). Now, When geo-replication status command is run, empty monitor status file gets created. Now, if glusterd is restarted, it reads empty monitor status and starts geo-replication session. This is incorrect as session was in Stopped state earlier. Solution: If monitor status is empty, error out and avoid starting geo-replication session. Note: if monitor status is empty, geo-rep session is displayed as Stopped state. Change-Id: Ifb3db896e5ed92b927764cf1163503765cb08bb4 BUG: 1351071 Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com> Reviewed-on: http://review.gluster.org/14830 Smoke: Gluster Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions