Our monitoring script runs:
gluster volume status all
and parses the output analyzing the volumes and the bricks. Of late one of the Gluster-servers here started replying to the above command with an error:
Another transaction is in progress. Please try again after sometime.
What's causing this condition and how do I clear it out? It, probably, will go away, if I restart the gluster-service completely, but we'd rather avoid such drastic a measure... Any suggestions?
We are on CentOS-6 using gluster-3.6.2 installed via RPMs published by gluster.org. Thanks!