Re: shrink changelogdb - Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/30/2015 12:54 PM, Jordan, Phillip wrote:

Can someone forward a link on how to shrink down the changelogdb, we tried the LDIF method  to create the values but the schema  is not present in the directory to create the object.  Does a better document exist or someone that has come across this same issue let me know.  Thanks in advance.

We are running 1.2.11.15 B2013.357.1711

1) Do you happen to have a plan to upgrade to 389-ds-base-1.3.2 or 1.3.3?  This feature is available on them.

    Ticket #197 - BDB backend - clear free page files to reduce changelog size
    https://fedorahosted.org/389/ticket/197
    2 config parameters are introduced to specify the interval of the
    compact calls.
    Primary DBs (id2entry):
      dn: cn=config,cn=ldbm database,cn=plugins,cn=config
      nsslapd-db-compactdb-interval: <seconds>
    Changelog DBs:
      dn: cn=changelog5,cn=config
      nsslapd-changelogcompactdb-interval: <seconds>
    By default, 2592000 seconds (30 days)

2) This config parameter "nsslapd-changelogmaxage (Max Changelog Age)" is available in 389-ds-base-1.2.11.  If not set, you may want to consider setting it.
Please see this doc section:
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Configuration_Command_and_File_Reference/Core_Server_Configuration_Reference.html#cnchangelog5-nsslapd_changelogmaxage_Max_Changelog_Age
But please note that the physical size of changelog db is not affected by the parameter.

3) If you do export and import back the main data without the state information (without -r option for db2ldif) on a master, and do consumer initialization against the other servers in the topology, the changelog dbs would be regenerated.  But it'd require quite a long down time...

 

 

Phillip Jordan

Lead Engineer, Web Hosting

 

555 W. Adams

Chicago, IL 60661

transunion.com

 

This email including, without limitation, the attachments, if any, accompanying this email, may contain information which is confidential or privileged and exempt from disclosure under applicable law. The information is for the use of the intended recipient. If you are not the intended recipient, be aware that any disclosure, copying, distribution, review or use of the contents of this email, and/or its attachments, is without authorization and is prohibited. If you have received this email in error, please notify us by reply email immediately and destroy all copies of this email and its attachments. 

 



--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux