[Bugs] [Bug 1342431] [georep]: Stopping volume fails if it has geo-rep session ( Even in stopped state)
bugzilla at redhat.com
bugzilla at redhat.com
Fri Jun 3 09:13:11 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1342431
Kotresh HR <khiremat at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|bugs at gluster.org |khiremat at redhat.com
--- Comment #1 from Kotresh HR <khiremat at redhat.com> ---
Description of problem:
=======================
Pre-requisite of stopping volume is to stop geo-rep session. Even if geo-rep
session is stopped, it fails complaining that the geo-rep session is ACTIVE.
[root at dhcp37-88 scripts]# gluster volume stop MASTER
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: MASTER: failed: geo-replication sessions are active for the volume
MASTER.
Stop geo-replication sessions involved in this volume. Use 'volume
geo-replication status' command for more info.
[root at dhcp37-88 scripts]# gluster volume geo-replication status
MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE
SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED
---------------------------------------------------------------------------------------------------------------------------------------------
10.70.37.88 MASTER /rhs/brick1/b1 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
10.70.37.88 MASTER /rhs/brick2/b4 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
10.70.37.213 MASTER /rhs/brick1/b3 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
10.70.37.213 MASTER /rhs/brick2/b6 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
10.70.37.43 MASTER /rhs/brick1/b2 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
10.70.37.43 MASTER /rhs/brick2/b5 root
ssh://10.70.37.52::SLAVE N/A Stopped N/A N/A
[root at dhcp37-88 scripts]# gluster volume list
MASTER
gluster_shared_storage
[root at dhcp37-88 scripts]#
Version-Release number of selected component (if applicable):
=============================================================
How reproducible:
=================
Always
Steps to Reproduce:
===================
1. Create geo-rep session between master and slave
2. Stop geo-rep session
3. Stop volume
Actual results:
===============
It fails complaining that the geo-rep session is active.
Expected results:
=================
Volume stop should succeed
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list