Red Hat Bugzilla – Bug 1030008
[Scale] Not Able To Start Volume (8-hosts, 8-bricks each host)
Last modified: 2015-05-13 12:34:35 EDT
Description of problem:
Attempting to start a volume that consists of 8-hosts and 8-bricks per host will not start.
Note: The configuration consists of a total of 8-volumes each with 8-hosts and 8-bricks per host.
Ovirt log message:
2013-11-13 11:36:55,195 INFO [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (ajp-/127.0.0.1:8702-7) [1fe610de] Failed to acquire lock and wait lock EngineLock [exclusiveLocks= key: 2806cc3f-25e6-4bc5-a413-cb32930e7ef3 value: GLUSTER
Error while executing action: A Request to the Server failed with the following Status Code: 500
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create 8 volumes with each volume consisting of 8-hosts with each host having 8-bricks
2. Start any volume
Volume does not start
Volume should start
Created attachment 823547 [details]
Note: The 64-Host and 8-Volume configuration was an Import Cluster operation. Neither the Hosts or Volumes were added/created with the Console.
We are not able to reproduce this error with the similar setup (64 Hosts and 8 Bricks per host and 8 Volumes with 64 bricks in each volume).
we were able to start and stop the volumes many times without any issue.
Still the issue is not reproducible with the given step. Always volume start/stop
works without any issue.
I can see from the log attached by Matt that most of the time gluster failed
to start the volume with error 'Another transaction is in progress'. I think this is normal and volume start/stop should work after some time.
Please verify once again with the same setup.
We are not able to reproduce this error with the current setup. We may try to
reproduce this Corbett setup.