Bug 764826 (GLUSTER-3094) - [FEAT] Allow bandwidth limiting or bandwidth shaping with geo-rep configuration
Summary: [FEAT] Allow bandwidth limiting or bandwidth shaping with geo-rep configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3094
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.2.1
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-27 18:53 UTC by Harshavardhana
Modified: 2015-03-23 01:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-11 16:16:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Harshavardhana 2011-06-27 18:53:44 UTC
Since geo-replication upper bounds itself with rsync --bwlimits option can be implemented to limit bandwidth in case of large file transfers so that the WAN link is not choked up.

Comment 1 Harshavardhana 2013-07-27 05:45:15 UTC
This particular feature currently works 

gsyncd.py --rsync-options '--sparse --bwlimits=<value>' 

Need a way to enable this through

$ gluster volume geo-replication <MASTER> <SLAVE> config rsync-options '--sparse --bwlimits=<value>'

Value has to be validated as KB/sec i.e Kilo-Bytes per second

Comment 2 Harshavardhana 2013-07-27 05:53:53 UTC
Just tested 

$ gluster volume geo-replication <MASTER> <SLAVE> config rsync_command 'rsync --sparse --bwlimits=<value>'

This seems to work, might not be necessary to provide any other options are this point - we could close this bug.

Comment 3 purpleidea 2014-03-18 15:41:32 UTC
As a side note, it is possible to do similar things at the firewall level with shorewall. I'd prefer doing it this way with rsync, but I figured I'd mention it.

Comment 4 purpleidea 2014-03-18 15:42:06 UTC
Also, the flag is --bwlimit not --bwlimits.

Comment 5 Venky Shankar 2014-03-18 15:57:06 UTC
(In reply to purpleidea from comment #4)
> Also, the flag is --bwlimit not --bwlimits.

Thanks for the correction :-)


Note You need to log in before you can comment on or make changes to this bug.