e264ca88e2
Swift doesn't recommend any rsync hostname allow/deny rules for inside your cluster network and I've never heard of anyone using it. The reverse lookup on connect (even those denied for max connections) can be overwhelming during a rebalance. Since rsync allows explicit control of the behavior after 3.1 we should suggest operators use it, It's also nominally more efficient in all cases. Possible drawback is maybe in the future a Swift operator has good reason to use host allow/deny rules and don't realize the rsync settings we recommend are mutually exclusive with their customizations. Change-Id: I2fdffdf1cc0a77f994c1d7894d5a1c8e5d951755
82 lines
1.8 KiB
Plaintext
82 lines
1.8 KiB
Plaintext
uid = swift
|
|
gid = swift
|
|
log file = /var/log/rsyncd.log
|
|
pid file = /var/run/rsyncd.pid
|
|
# since rsync default for reverse lookup is true, you have to set it to false
|
|
# here globally or after a few 100 nodes your dns team will fuss at you
|
|
reverse lookup = false
|
|
|
|
[account]
|
|
max connections = 2
|
|
path = /srv/node
|
|
read only = false
|
|
lock file = /var/lock/account.lock
|
|
|
|
[container]
|
|
max connections = 4
|
|
path = /srv/node
|
|
read only = false
|
|
lock file = /var/lock/container.lock
|
|
|
|
[object]
|
|
max connections = 8
|
|
path = /srv/node
|
|
read only = false
|
|
lock file = /var/lock/object.lock
|
|
|
|
|
|
# If rsync_module includes the device, you can tune rsyncd to permit 4
|
|
# connections per device instead of simply allowing 8 connections for all
|
|
# devices:
|
|
# rsync_module = {replication_ip}::object_{device}
|
|
#
|
|
# (if devices in your object ring are named sda, sdb and sdc)
|
|
#
|
|
#[object_sda]
|
|
#max connections = 4
|
|
#path = /srv/node
|
|
#read only = false
|
|
#lock file = /var/lock/object_sda.lock
|
|
#
|
|
#[object_sdb]
|
|
#max connections = 4
|
|
#path = /srv/node
|
|
#read only = false
|
|
#lock file = /var/lock/object_sdb.lock
|
|
#
|
|
#[object_sdc]
|
|
#max connections = 4
|
|
#path = /srv/node
|
|
#read only = false
|
|
#lock file = /var/lock/object_sdc.lock
|
|
|
|
|
|
# On a swift-all-in-one VM, you might tune rsync by replication port instead:
|
|
# rsync_module = {replication_ip}::object{replication_port}
|
|
#
|
|
# So, on your SAIO, you have to set the following rsyncd configuration:
|
|
#
|
|
#[object6010]
|
|
#max connections = 25
|
|
#path = /srv/1/node/
|
|
#read only = false
|
|
#lock file = /var/lock/object6010.lock
|
|
#
|
|
#[object6020]
|
|
#max connections = 25
|
|
#path = /srv/2/node/
|
|
#read only = false
|
|
#lock file = /var/lock/object6020.lock
|
|
#
|
|
#[object6030]
|
|
#max connections = 25
|
|
#path = /srv/3/node/
|
|
#read only = false
|
|
#lock file = /var/lock/object6030.lock
|
|
#
|
|
#[object6040]
|
|
#max connections = 25
|
|
#path = /srv/4/node/
|
|
#read only = false
|
|
#lock file = /var/lock/object6040.lock
|