Hi,
I've run into a situation where one of the files in /var/lib/dirsrv/<instance>/changelogdb has grown almost as large as the partition it's on. In my directory server configs, I noticed I was keeping an unlimited changelog, so I set that to what seems like a reasonably long amount of time (18 weeks) but didn't see any decrease in the file size. I'm wondering now about the best course of action. I can
a) move the whole dirsrv directory to another partition with more space available and symlink the old location to the new, which worked when I tested it, but I wanted to make sure I wouldn't be hosing something up the next time I upgrade.
b) find some means of manually shrinking the *.db ( can you even do that?)
c) point dirsrv at a new location, and reinitialize the consumers (which doesn't seem all that desirable)
Has anyone else found it necessary to shrink your changelogdb?
Thanks
-Tim
Hartmann, Tim wrote:
Hi,
I've run into a situation where one of the files in /var/lib/dirsrv/<instance>/changelogdb has grown almost as large as the partition it's on. In my directory server configs, I noticed I was keeping an unlimited changelog, so I set that to what seems like a reasonably long amount of time (18 weeks) but didn't see any decrease in the file size. I'm wondering now about the best course of action. I can
http://www.redhat.com/docs/manuals/dir-server/8.1/cli/Configuration_Command_...
a) move the whole dirsrv directory to another partition with more space available and symlink the old location to the new, which worked when I tested it, but I wanted to make sure I wouldn't be hosing something up the next time I upgrade.
If you have a large database with a large number of updates, it's probably a good idea to have the changelog on a separate partition anyway.
I think that what you have done will work.
b) find some means of manually shrinking the *.db ( can you even do that?)
Not the changelog db.
c) point dirsrv at a new location, and reinitialize the consumers (which doesn't seem all that desirable)
Also a possibility, but as you say, undesirable.
Has anyone else found it necessary to shrink your changelogdb?
Thanks
-Tim
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
2010/4/12 Hartmann, Tim hartmann@fas.harvard.edu:
Hi,
I've run into a situation where one of the files in /var/lib/dirsrv/<instance>/changelogdb has grown almost as large as the partition it's on. ... Has anyone else found it necessary to shrink your changelogdb?
-Tim
Yes, I have the same problem, changelogdb is about 13Gb (I have 10000 entries in my environment, 2 node MMR) and my partition has less than 10% free space.
I have added attributes nsslapd-changelogmaxage: 4w and nsslapd-changelogmaxentries: 5000
to cn=changelog5,cn=config and restarted both servers.
Should it shrink now automatically or do I need to do something else?
Regards, Kimmo
On 09/09/2010 08:00 AM, Kimmo Koivisto wrote:
I've run into a situation where one of the files in/var/lib/dirsrv/<instance>/changelogdb has grown almost as large as the partition it's on.
... Has anyone else found it necessary to shrink your changelogdb?
-Tim
Yes, I have the same problem, changelogdb is about 13Gb (I have 10000 entries in my environment, 2 node MMR) and my partition has less than 10% free space.
I have added attributes nsslapd-changelogmaxage: 4w and nsslapd-changelogmaxentries: 5000
to cn=changelog5,cn=config and restarted both servers.
Should it shrink now automatically or do I need to do something else?
I believe it will stay to the same file size / will not shrink although it is slowly trimmed as entries are cleared but not released. M.
389-users@lists.fedoraproject.org