Thanks for the suggestion, this solved it for us, and we probably found the cause as well. We had performance co-pilot running and it was continously enabling profiling on volumes...
We found the reference to the node that had the lock, and restarted glusterd on that node, and all went well from there on.On 31 May 2017 at 15:56, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
On Wed, May 31, 2017 at 9:32 AM, Krist van Besien <krist@xxxxxxxxxx> wrote:What do these messages mean? How do I figure out which "transaction" is meant here, and what do I do about it?These messages pop up, then disappear for a while, then pop up again..."Another transaction is in progres for <some volume>"Hi all,I am trying to do trivial things, like setting quota, or just querying the status and keep gettingThis message usually means that a different gluster command is being executed in the cluster. Most gluster commands are serialized by a cluster wide lock. Upon not being able to acquire the cluster lock, this message is displayed.You can check /var/log/glusterfs/cmd_history.log on all storage nodes to observe what other commands are in progress at the time of getting this error message. Are you per chance using oVirt to manage Gluster? oVirt periodically does a "gluster volume status" to determine the volume health and that can conflict with other commands being executed. Regards,Vijay
--
Vriendelijke Groet | Best Regards | Freundliche Grüße | Cordialement
Krist van Besien | Senior Architect | Red Hat EMEA Cloud Practice | RHCE | RHCSA Open Stack
Krist van Besien | Senior Architect | Red Hat EMEA Cloud Practice | RHCE | RHCSA Open Stack
@: krist@xxxxxxxxxx | M: +41-79-5936260
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
