Description of problem:
When the zone is switched from master to non-master, all I/O requests hang until a rgw process restart on both the zones
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Modify non-master zone with '--master' flag.
radosgw-admin zone modify --rgw-zonegroup=us --rgw-zone=us-2
--access_key=secret --secret=secret --endpoints=http://magna059:80 --default
2. Update and commit the period
A radosgw restart should not be expected with a period configuration change. However all the I/O's hang until a process restart.
Traceback (most recent call last):
File "s3del.py", line 21, in <module>
File "/usr/lib/python2.7/site-packages/boto/s3/connection.py", line 641, in delete_bucket
response = self.make_request('DELETE', bucket, headers=headers)
File "/usr/lib/python2.7/site-packages/boto/s3/connection.py", line 668, in make_request
File "/usr/lib/python2.7/site-packages/boto/connection.py", line 1071, in make_request
File "/usr/lib/python2.7/site-packages/boto/connection.py", line 1028, in _mexe
raise BotoServerError(response.status, response.reason, body)
boto.exception.BotoServerError: BotoServerError: 504 Gateway Time-out
<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
We have upstream testing that makes multiple changes to the master zone without restarting gateways, and we haven't seen it hit this issue. Can you try to reproduce the issue with the latest build?
(In reply to Casey Bodley from comment #7)
> Hi Shilpa,
> We have upstream testing that makes multiple changes to the master zone
> without restarting gateways, and we haven't seen it hit this issue. Can you
> try to reproduce the issue with the latest build?
Sure, I will try it on 2.0 Async build?
Verified on 10.2.3-12. No gateway restart is required to switch master.
It looks good to me.
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.