Bug 1026854 - [RHSC][scale-test] Volume Create Error "Another transaction is in progress"
Summary: [RHSC][scale-test] Volume Create Error "Another transaction is in progress"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 2.1.2
Assignee: Shubhendu Tripathi
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 14:28 UTC by Matt Mahoney
Modified: 2023-09-14 01:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-27 11:56:00 UTC
Embargoed:
mmahoney: needinfo+


Attachments (Terms of Use)
Volume Create Error (2.96 MB, application/x-gzip)
2013-11-05 14:28 UTC, Matt Mahoney
no flags Details

Description Matt Mahoney 2013-11-05 14:28:10 UTC
Created attachment 819800 [details]
Volume Create Error

Description of problem:
During a 4-user concurrency test, volume create error occurred twice during the test testing session:

ERROR - Error while executing action Create Gluster Volume: Volume create failed error: Another transaction is in progress_ Please try again after sometime_ return code: -1

Note: Each of the 4-users were creating volumes on different clusters.

Version-Release number of selected component (if applicable):
Big Bend

How reproducible:


Steps to Reproduce:
1. Two+ users concurrently creating volumes.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Sahina Bose 2013-11-08 06:06:20 UTC
I don't see any errors in logs, however the error message indicates that this is an error thrown from gluster preventing concurrent operations.

Comment 3 Shubhendu Tripathi 2013-11-20 11:02:21 UTC
Matt, can you share the setup details how the concurrent volume creation is being tried out.
I would like to simulate the issue using the same.

Comment 5 Shubhendu Tripathi 2013-11-26 14:13:44 UTC
Matt,

I was able to add four volumes from four different browser sessions simultaneously without any error in a single cluster. It correctly tries acquiring the lock for creation of volume and messages can be seen in engine.log.

Let me know if you used any other mechanism for firing the parallel creation of volumes.

Also as mentioned by Sahina, the error message mentioned in the bug description is from GLUSTER which gets propagated to VDSM and then to engine UI. So in some race condition if gluster gives that error during volume creation, the same is being displayed properly in UI which is expected behaviour.

May be try simulating once the issue once more and let me know if some other way of parallel volume creation is used here.

Comment 6 Red Hat Bugzilla 2023-09-14 01:53:09 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.