When gluster geo-replication is configured between two sites, the geo-rep session could consume more WAN bandwidth than a customer desires. Though throttling at the firewall or router level may be an option, it's network team and network vendor dependent. The ask here is to implement some form of bandwidth throttling between one gluster environment to another, so that a geo-rep session may be capped at a total amount of bandwidth consumed.
we already have support via rsync option. Since geo-rep by default uses rsync to sync the files from master to slave, we can use rsync option to limit the bandwidth usage. gluster volume geo-replication <master_volume> <SlaveHost::Slave_volume> config rsync-options "--bwlimit=<value>"
rsync-options is only useful when rsync is used as sync engine, will not work when use_tarssh is used.
Verified with build: glusterfs-3.7.1-9.el6rhs.x86_64 Setting bwlimit is successful and rsync uses that as parameter during sync. Moving this bug to verified state.
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/RHSA-2015-1495.html