Hi all,
I have multisite RGW setup with one zonegroup and two zones. Each zone has
one endpoint configured like below:
"zonegroups": [
{
...
"is_master": "true",
"endpoints": ["http://192.168.100.1:80";],
"zones": [
{
"name": "primary_1",
"endpoints": ["http://192.168.100.1:80";]
We used to have issues when a load balancer was in front of the sync
endpoints, because our http client didn't time out stalled connections.
Those are resolved in luminous, but we still recommend using the radosgw
addresses directly to avoid shoveling data through an extra proxy.
Internally, sy
Hi,
Is there any mechanism inside the rgw that can detect faulty endpoints
for a configuration with multiple endpoints?
Is there any advantage related with the number of replication
endpoints? Can I expect improved replication performance (the more
synchronization rgws = the faster replication)?
Hi,
Is there any mechanism inside the rgw that can detect faulty endpoints for
a configuration with multiple endpoints?
Is there any advantage related with the number of replication endpoints?
Can I expect improved replication performance (the more synchronization
rgws = the faster replication)?
On 7/17/19 8:04 AM, P. O. wrote:
Hi,
Is there any mechanism inside the rgw that can detect faulty endpoints
for a configuration with multiple endpoints?
No, replication requests that fail just get retried using round robin
until they succeed. If an endpoint isn't available, we assume it will
Hi,
I also have been looking solutions for improving sync. I have two clusters, 25
ms RTT, with the RGW multi-site configured and all nodes running 12.2.12. I
have three rgw nodes at each with the nodes behind haproxy at each site. There
is a 1G circuit between the sites and bandwidth usage