Re: Re: Removing Berkeley DB Log Files

To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>

Subject: Re: Re: Removing Berkeley DB Log Files

From: Douglas Duckworth <dod2014@med.cornell.edu>

Date: Thu, 31 Aug 2017 11:30:14 -0400

Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=medcornell.onmicrosoft.com; s=selector1-med-cornell-edu; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Rtx8ylF58hVKBFFiw8cUZ2PlWgRcpDEh7ViqmnFwrPY=; b=ds/4sdfKzZj7Uueob+ANz8w4inzxS/3rsLJ7Yl2MUkUu9bVfj8kRnzRaPJtIA+/0O7/im0fdgrA7jXhzSbKuFDJBlOYUuWWdQiEKudq4EROCpQImucSmxONA6K/JnMobQgb6YEw5zFk15COumg2EPMBt3/auUAO5fbTc+2FBHNw=

In-reply-to: <4d9df8ff2f3045ef90d2c3c2ddab15e7@DM5PR06MB3097.namprd06.prod.outlook.com>

References: <CAAKHBKkySH++oJ3Uue2HK7P7wRVuEPyWWdSrqzxEQJFQmavYjw@mail.gmail.com> <WM!7c09644533545470ed1a815bc81ad7c4eb7ec22a32671e1833cfe0c920ae0424f3a2688c0048a82d9c498526b9656b30!@mailstronghold-2.zmailcloud.com> <1af444e5f795475988cdce24dd419fd8@DM5PR06MB3097.namprd06.prod.outlook.com> <CAAKHBK=Uac0x9iEz9N363hb1sgfKPEhjP_dArOH05NFDkUWXDA@mail.gmail.com> <CAAKHBKnJHcSJLn5aBpEaLsvScmGka0Jt5X02HLxsgK9+LTLDMw@mail.gmail.com> <CAAKHBKm0FKBR4BLNpy6jrszFp35Eid_J2F19MKmfS+G47EKCJA@mail.gmail.com> <4d9df8ff2f3045ef90d2c3c2ddab15e7@DM5PR06MB3097.namprd06.prod.outlook.com>

Spamdiagnosticmetadata: NSPM

Spamdiagnosticoutput: 1:99

Thanks, a lot everyone!

Performance looks good now. No deadlocks and nothing being purged from the cache. I have started pointing more sssd clients at the cluster.

Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit

Physiology and Biophysics

Weill Cornell Medicine

E: doug@med.cornell.edu
O: 212-746-6305
F: 212-746-8690

On Thu, Aug 31, 2017 at 2:51 AM, Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> wrote:

>>> Douglas Duckworth <dod2014@med.cornell.edu> schrieb am 30.08.2017 um 16:06 in
Nachricht
<CAAKHBKm0FKBR4BLNpy6jrszFp35Eid_J2F19MKmfS+G47EKCJA@mail.gmail.com>:
[...]
> Only four clients are currently using this cluster so perhaps I should
> actually use DB_CONFIG before putting it into production.

Maybe you could start considering this from a moderately loaded and sized server:
set_cachesize 0 15000000 1
set_lg_regionmax 262144
set_lg_bsize 2097152
set_flags DB_LOG_AUTOREMOVE
set_lk_max_locks 30000
set_lk_max_objects 30000
---

Also note "olcDbConfig: <DB_CONFIG setting>" is probably the modern way to do it.

Regards,
Ulrich

References:

Removing Berkeley DB Log Files
- From: Douglas Duckworth <dod2014@med.cornell.edu>
Re: Removing Berkeley DB Log Files
- From: Douglas Duckworth <dod2014@med.cornell.edu>
Re: Removing Berkeley DB Log Files
- From: Douglas Duckworth <dod2014@med.cornell.edu>
Re: Removing Berkeley DB Log Files
- From: Douglas Duckworth <dod2014@med.cornell.edu>