summaryrefslogtreecommitdiffstats
path: root/libgfdb.pc.in
diff options
context:
space:
mode:
authorSaravanakumar Arumugam <sarumuga@redhat.com>2015-08-10 18:42:05 +0530
committerJeff Darcy <jdarcy@redhat.com>2015-09-01 06:11:01 -0700
commit4d4c7d5dc54850dcf916083b2b1398d9bfe2bfe6 (patch)
treefd6fc9252c75fcc67a3174ae61b476373f4dca13 /libgfdb.pc.in
parentd713488e47a384814e55b484f9a7e81664021d52 (diff)
geo-rep: Update geo-rep status, if monitor process is killed
Problem: When the monitor process itself is getting killed, geo-rep session still shows as active. Status command will just pick up the content from the status file to show the output. Monitor process is the one which updates the Status file. When the monitor process itself gets killed, there is no way to update the status file. So, geo-rep session status command ends up showing last updated Status present in the status file. Solution: While getting the status output, check whether monitor process is running. If it is NOT running, update the status as STOPPED. Change-Id: I86a7ac1746dd8f27eef93658e992ef16f6068d9d BUG: 1251980 Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com> Reviewed-on: http://review.gluster.org/11873 Tested-by: NetBSD Build System <jenkins@build.gluster.org> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Milind Changire <mchangir@redhat.com> Reviewed-by: Kotresh HR <khiremat@redhat.com> Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
Diffstat (limited to 'libgfdb.pc.in')
0 files changed, 0 insertions, 0 deletions