+++ This bug was initially created as a clone of Bug #1454872 +++ 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:
Patch merged upstream long back and it would come to 3.4 as part of rebase. https://review.gluster.org/17376
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://access.redhat.com/errata/RHSA-2018:2607