Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 764826 (GLUSTER-3094)

Summary:	[FEAT] Allow bandwidth limiting or bandwidth shaping with geo-rep configuration
Product:	[Community] GlusterFS	Reporter:	Harshavardhana <fharshav>
Component:	geo-replication	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.2.1	CC:	cww, gluster-bugs, kbudiger, purpleidea, rwheeler, vagarwal, vshankar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-11 16:16:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 :-)