Recommend better rsync.conf settings

Code Issues Proposed changes

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

This commit is contained in:

Clay Gerrard

2020年03月19日 19:15:03 -05:00

parent 9d4dc29fb3

commit e264ca88e2

1 changed files with 3 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

3
etc/rsyncd.conf-sample

View File

@@ -2,6 +2,9 @@ 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

Recommend better rsync.conf settings

3 etc/rsyncd.conf-sample Unescape Escape View File

3
etc/rsyncd.conf-sample

View File