DS 5.2 tran log processing
I am replicating between two masters on a Sun 5.2 system.
When processing a large number of updates , I am seeing
large growth in the transaction logs of both systems. Eventually
these transaction logs will be processed. We are talking as
much as a gigabyte of space.
However , on at least one system I am relatively space constrained .
Is ther a system parameter that I can apply to both systems that
will cause the DS to clean up these logs quicker. I realize that this will
slow thruput of batch processing.
I n the past I have nearly run out of disk space with the current configuration.
Thanks
JYArd
UCLA
[691 byte] By [
JohnYarda] at [2007-11-27 8:56:24]
# 2
Also changelogs in a multi-master environment. An issue is the changelogdb; I have about 2 G on each system, and they never shrink
back to their original size. This system must be 24 x 7, is there a way
to shrink or resize the changelog w/o system downtime ? This
would free up 2G, I believe the changelog sizre expanded to it's current size during the initial data load 1 yr ago,
JYard
UCLA
# 5
5 days is already pretty low, so I would think you wouldn't get a much smaller changelog by going lower.
I suggested you check it because the default setting is unlimited, which allows the changelog to grow forever. But sounds like you already have this base covered.
2 GB does seem pretty high if the old stuff is getting pruned out after 5 days. Hopefully someone else can comment on this.
# 7
> What is happening is that this is nort freeing
> space.
> I believe all of this is from an initial load 1 year
> ago;
> if I change 5 days to 8 hours will thsi free the
> space ?
>
> JYard
Not in the 5.x version .. unfortunately. Due to the way the Sleepycat (Berkeley) database works the changelog DB will never shrink to a smaller size than what has already been reached.
Cleaning the changelog is basically removing the changelog after making sure that all changes within the changelog DB have been replicated to all consumers.
After cleaning you may use the nsslapd-changelogmaxage and/or nsslapd-changelogmaxentries attribute(s) to limit the size of your future changelog db.
