Bug 1454872

Summary:	[Geo-rep]: Make changelog batch size configurable
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1503167 (view as bug list)		Environment:
Last Closed:	2017-09-05 17:31:32 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:
Bug Blocks:	1503167, 1531940, 1531941

Description Kotresh HR 2017-05-23 16:01:23 UTC

Description of problem:
As of now, changelog batch size is constant (727040 bytes) which is size of all changelogs together in a single batch. Make it configurable to gain more control in the interval of stime updation.

Version-Release number of selected component (if applicable):
master

Actual results:
Changelog batch size fixed.

Expected results:
We should configurable something like

gluster vol geo-rep <mastervol> <slavehost>::<slavevol> config changelog-batch-size <num>

Additional info:

Comment 1 Worker Ant 2017-05-23 16:02:56 UTC

REVIEW: https://review.gluster.org/17376 (geo-rep: Make changelog-batch-size configurable) posted (#1) for review on master by Kotresh HR (khiremat)

Comment 2 Worker Ant 2017-05-24 06:12:06 UTC

COMMIT: https://review.gluster.org/17376 committed in master by Aravinda VK (avishwan) 
------
commit 0bcf9143f500dd519c887af2b6948e2d332b3bfd
Author: Kotresh HR <khiremat>
Date:   Tue May 23 11:47:18 2017 -0400

    geo-rep: Make changelog-batch-size configurable
    
    Changelog batch size is set to 727040 bytes which
    is the size of all the changelogs in a single batch.
    It's based on few tests which approximately processes
    5K entries. But it might vary on different machines.
    Making it configurable gives more control on the
    frequency of stime updates. This patch does the same.
    
    Change-Id: I9a5ebb3d92c1327dded0e0a712c43a5a9046c1b0
    BUG: 1454872
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: https://review.gluster.org/17376
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Amar Tumballi <amarts>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>

Comment 3 Shyamsundar 2017-09-05 17:31:32 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report.

glusterfs-3.12.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-September/000082.html
[2] https://www.gluster.org/pipermail/gluster-users/