Bug 1441946 - Brick Multiplexing: volume status showing "Another transaction is in progress"
Summary: Brick Multiplexing: volume status showing "Another transaction is in progress"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.3.0
Assignee: Atin Mukherjee
QA Contact: Vinayak Papnoi
URL:
Whiteboard:
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-04-13 07:28 UTC by Nag Pavan Chilakam
Modified: 2018-11-30 05:38 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.8.4-23
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 04:37:54 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1441932 0 unspecified CLOSED Gluster operations fails with another transaction in progress as volume delete acquires lock and won't release 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Internal Links: 1441932

Description Nag Pavan Chilakam 2017-04-13 07:28:23 UTC 
With Brick Multiplexing enabled, I keep getting Another transaction is in progress for <volname>. Please try again after sometime. 
I see this problem multiple times, but inconsistent

version:
3.8.4-22

Setup details :
same as BZ#1441939 - Brick Multiplexing: Ended up with two brick processes on multiplexing setup
Comment 2 Nag Pavan Chilakam 2017-04-13 07:29:26 UTC 
checked for two different volumes and got below errors

[root@dhcp35-112 ~]# gluster v status cross3_54
Another transaction is in progress for cross3_54. Please try again after sometime.
[root@dhcp35-112 ~]# gluster v status cross3_53
Error : Request timed out
[root@dhcp35-112 ~]#
Comment 3 Atin Mukherjee 2017-04-13 08:38:52 UTC 
upstream patch : https://review.gluster.org/#/c/17055/
Comment 4 SATHEESARAN 2017-04-17 13:27:12 UTC 
(In reply to Atin Mukherjee from comment #3)
> upstream patch : https://review.gluster.org/#/c/17055/

Hi Atin,

The consequence of this bug is same as 1441932 , why can't this bug be CLOSED as the DUP of 1441932 ?
Comment 7 Atin Mukherjee 2017-04-18 11:25:59 UTC 
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/103636
Comment 10 Vinayak Papnoi 2017-06-14 10:12:25 UTC 
Gluster version : 3.8.4-26

Created volumes, mounted and took a snapshot of it. Then did a "gluster v status <volname>" on a loop for 100 times.

Result: The status was displayed normally without any error message.

Hence, moving this bug to verified.
Comment 12 errata-xmlrpc 2017-09-21 04:37:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774
Note You need to log in before you can comment on or make changes to this bug.