Closed 389-ds-bot closed 4 years ago
Comment from mreynolds (@mreynolds389) at 2018-12-20 17:58:25
Metadata Update from @mreynolds389:
Comment from firstyear (@Firstyear) at 2019-02-04 02:33:42
I don't think this should be set while running because this would break out bdb env, and really serves little utility. I thinkk this is an offline only operation.
@mmuehlfeldrh Can we fix this in the docs?
Comment from firstyear (@Firstyear) at 2019-03-12 03:24:29
Ping @mmuehlfeldrh or @mreynolds389 ?
Comment from mmuehlfeldrh at 2019-03-12 09:29:46
Sorry, I missed this. I updated the step of the procedure: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/performance_tuning_guide/tuning-db-cache#db-cache-on-ram-disk
I cannot update the metadata of this BZ. The Red Hat BZ number is 1687701.
Comment from firstyear (@Firstyear) at 2019-03-13 02:32:41
Awesome, thank you!
Comment from firstyear (@Firstyear) at 2019-03-13 02:32:41
Metadata Update from @Firstyear:
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50047
Issue Description
Currently,
nsslapd-db-home-directory
is not allowed to be set when 389 is running:This conflicts with the documentation as well: https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/performance_tuning_guide/#db-cache-on-ram-disk
Ideally, this setting is allowed to be configured but is one of the requires restart settings. Currently, you must stop dirsrv, manually add this to your dse.ldif and then start it.
Package Version and Platform
Operating System: CentOS 7
Steps to reproduce
nsslapd-db-home-directory
Actual results
Changing
nsslapd-db-home-directory
on a running dirsrv instance fails completely.Expected results
nsslapd-db-home-directory
should be updated but only be used after restart. Even more ideally would be to not require the restart at all but, I'm sure that's way more complicated and unnecessary to implement.