Description of problem: Geo-Replication status says "warning" and status informtion says "georeplication status could not be determined - Another transaction is in progress for vol_repmaster.Please try again after some time" Version-Release number of selected component (if applicable): nagios-server-addons-0.1.3-3.el6rhs.x86_64 gluster-nagios-common-0.1.3-1.el6rhs.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Inconsistently reproducible.
From kanagaraj, i understand that these bugs have been moved to on_qa by errata. Since QE has not yet received the build i am moving this bug back to assigned state. Please move it on to on_qa once builds are attached to errata.
Sahina, I see that status and status information gets displayed as below: status - UNKNOWN status Information - temporary error. Another transaction is in progress for <vol_name>. Please try again after some time. Is this the expected status information? AFAIK, status information should say "temporary error". Could you please confirm on this?
The fix is that this error should not be returned frequently - as the fix retries the geo-replication status command on other nodes in the gluster, till all nodes are exhausted. Could you check with > 4 node cluster in the master side and see how frequently you run into this?
I could still see for geo-replication service that status goes to 'UNKNOWN' with status information 'UNKNOWN- temporary error. Another transaction is in progress for <vol_name>. Please try again after some time.' Moving this bug back to assigned.
http://review.gluster.org/#/c/9192/ - patch submitted to intoduce a sleep for 2 seconds, when the volume is locked and transaction in progress errors are returned. However, this is not a foolproof way - but reduces the chances of such errors in Nagios plugins
Moving this bug back because geo-rep status gives the status as warning with status information as "null".
http://review.gluster.org/#/c/9226/ - fixing the issue with string comparison
Verified and works fine with build nagios-server-addons-0.1.11-1.el6rhs.noarch. I have not seen the issue with status as warning and status information as null. Will reopen this, if i see it again.
Hi Sahina, Can you please review the edited doc text for technical accuracy and sign off?
Minor edit done - signing off
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://rhn.redhat.com/errata/RHBA-2015-0039.html