[389-users] Re: autosizing the cache

> I don't believe autotuning exists in 1.3.5, it was only added to 1.3.6 - > sorry :-/ Ah, that makes my life a bit simpler for now :) >> Also, is there a way to check that auto-tuning is working normally? Is >> dbmon.sh the right way? > The error log at startup will tell you what the server

[389-users] Re: autosizing the cache

On 03/01/2018 03:18 PM, Sergei Gerasenko wrote: > Cool. The default setup of 389-ds (version 1.3.5.10) I don’t see > either |nsslapd-cache-autosize or ||nsslapd-cache-autosize-split. > Should I just add them to the dse file?| |I don't believe autotuning exists in 1.3.5, it was only added to

[389-users] Re: autosizing the cache

Cool. The default setup of 389-ds (version 1.3.5.10) I don’t see either nsslapd-cache-autosize or nsslapd-cache-autosize-split. Should I just add them to the dse file? > Correct, set them to 0 for autotuning to take effect The Redhat docs are a bit confusing on this

[389-users] Re: autosizing the cache

On 03/01/2018 02:32 PM, Sergei Gerasenko wrote: > Hello, > > My cn=userRoot,cn=ldbm database,cn=plugins,cn=config is currently: > > ... > nsslapd-cachesize: -1 > nsslapd-cachememsize: 1543503872 > nsslapd-readonly: off > nsslapd-require-index: off > nsslapd-dncachememsize: 5 > … > > But

[389-users] autosizing the cache

Hello, My cn=userRoot,cn=ldbm database,cn=plugins,cn=config is currently: ... nsslapd-cachesize: -1 nsslapd-cachememsize: 1543503872 nsslapd-readonly: off nsslapd-require-index: off nsslapd-dncachememsize: 5 … But cn=config,cn=ldbm database,cn=plugins,cn=config has these settings: ...

[389-users] Re: replication issue

Thank you William! That is great advice, and thank you for the link to the documentation. -Jesse On Wed, Feb 28, 2018 at 6:29 PM, William Brown wrote: > On Wed, 2018-02-28 at 11:45 -0500, JESSE LUNT wrote: > > Hey Kevin, > > > > > > I am doing a one-way