Bug 1160790

Summary:	RFE: bandwidth throttling of geo-replication
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	James Rankin <jrankin>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	rhgs-3.0	CC:	aavati, annair, avishwan, csaba, nlevinki, rhinduja
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHGS 3.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	usability
Fixed In Version:	glusterfs-3.7.0-2.el6rhs	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 04:36:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1168108
Bug Blocks:	1202842, 1223636

Description James Rankin 2014-11-05 15:54:47 UTC

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.

Comment 3 Aravinda VK 2014-11-06 11:41:20 UTC

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>"

Comment 4 Aravinda VK 2014-11-06 11:43:26 UTC

rsync-options is only useful when rsync is used as sync engine, will not work when use_tarssh is used.

Comment 9 Rahul Hinduja 2015-07-15 08:22:32 UTC

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.

Comment 12 errata-xmlrpc 2015-07-29 04:36:45 UTC

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