[Bugs] [Bug 1479664] create update delete 100 volumes, at last there are 4 volumes left

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1479664

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2017-08-16 04:01:22



--- Comment #4 from Atin Mukherjee <amukherj at redhat.com> ---
This is not a bug. What has happened is the volumes which are still visible
through gluster volume list were never deleted as the delete operation on the
volumes failed. For eg:

from 136.136.136.146

[2017-08-09 02:53:52.693510]  : volume stop
05fccafb-810b-4dab-8f24-7149617afa9f : FAILED : Another transaction is in
progress for     05fccafb-810b-4dab-8f24-7149617afa9f. Please try again after
sometime.                                                                 
[2017-08-09 02:53:52.722636]  : volume delete
05fccafb-810b-4dab-8f24-7149617afa9f : FAILED : Another transaction is in
progress for   05fccafb-810b-4dab-8f24-7149617afa9f. Please try again after
sometime.


Now why that can happen is when two nodes try to initiate transaction on the
same volume, one of them would succeed and one of them wouldn't. From the other
node's cmd_history.log file I can see that at the same time volume status
command was triggered which resulted into glusterd taking lock on the volume
05fccafb-810b-4dab-8f24-7149617afa9f in this node and this resulted into volume
stop and delete to fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.