[Bugs] [Bug 1175754] [SNAPSHOT]: before the snap is marked to be deleted if the node goes down than the snaps are propagated on other nodes and glusterd hungs
bugzilla at redhat.com
bugzilla at redhat.com
Tue Jan 6 10:18:37 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1175754
Raghavendra Bhat <rabhat at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rabhat at redhat.com
--- Comment #6 from Raghavendra Bhat <rabhat at redhat.com> ---
+++ This bug was initially created as a clone of Bug #1104714 +++
+++ This bug was initially created as a clone of Bug #1104635 +++
Description of problem:
=======================
In a case where the snap delete is issued before the snap is marked to be
deleted if the node goes down and when the node comes back than the snaps are
propagated on other nodes and glusterd hungs.
Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.6.1
Steps to Reproduce:
===================
1. Setup 4 node cluster
2. Create a volume
3. Create 256 snapshots of a volume
4. Start deleting snapshots of volume in a loop (--mode=script)
5. While snap deletion is in-progress, stop and start glusterd service on node
multiple times.
Actual results:
===============
1. Snapshot commit failed on the node which went down.
2. Once the node is brought back the snap is present on all the systems and no
entry in the missed_entry_list.
3. gluster hungs on the machines which were up
Expected results:
=================
1. Snapshot should fail with proper message.
2. Once the node is brought back the snap should be deleted from all the nodes.
3. gluster should not hung.
Since, it just not hamper the missed snap functionality but also the whole
cluster becomes unresponsive, raising the bug with urgent severity
--
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