Issue 7900 - N-Way Multi-Master replication file size
Summary: N-Way Multi-Master replication file size
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: 2.4.39
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-18 14:14 UTC by majain@verisign.com
Modified: 2020-03-20 20:51 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description majain@verisign.com 2014-07-18 14:14:40 UTC 
Full_Name: Mahendra Jain
Version: 2.4.39
OS: RHEL 6.4
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (216.168.230.7)


I've setup 3 masters using N-Way Multi-Master replication scheme. I'm sending
test load (write requests) using ldapadd to master 1. 

At the end of test, the data file size are compared on all the 3 master servers
as below:

Master 1: 80mb
Master 2: 700mb
Master 3: 2.1gb

The row count is also compared on all the 3 masters and they are all same (58000
row).

My question is what makes data files on master 2 and 3 to grow exponentially.

The database is configured to use mdb with maxsize set to 10737418240.

Thanks,
Mahendra
Comment 1 Quanah Gibson-Mount 2020-03-20 20:51:29 UTC 
This has largely been addressed in work since this release.