Thank you, one more question on mdb side, may be last question :)
How can i migrate/convert from hdb/bdb to mdb?
Ram
On Tue, Oct 3, 2017 at 11:09 AM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Tuesday, October 03, 2017 11:47 AM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Ok, but are there any casses where DB size can grow bigger then RAM and
>> what will happen in that case?
>>
>
> Same thing that happens in any such case.. it'll start swapping.
>
>
> --Quanah
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Tuesday, October 03, 2017 12:29 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Thank you, one more question on mdb side, may be last question :)
>
>
> How can i migrate/convert from hdb/bdb to mdb?
Generally, you slapcat your existing HDB database to an LDIF file, update
your configuration for slapd to use MDB instead, and then use slapadd to
import the LDIF file.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Tuesday, October 03, 2017 11:47 AM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Ok, but are there any casses where DB size can grow bigger then RAM and
> what will happen in that case?
Same thing that happens in any such case.. it'll start swapping.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Ok, but are there any casses where DB size can grow bigger then RAM and
what will happen in that case?
On Oct 3, 2017 10:18 AM, "Quanah Gibson-Mount" <quanah(a)symas.com> wrote:
> --On Tuesday, October 03, 2017 11:03 AM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Quanah,
>>
>>
>> Quick question regarding "maxsize" in mdb, slapd-mdb man page says we
>> have to preallocate the db size based on future growth of your data, that
>> means will it create a data.mdb of maxsize? what i read from docs is, mdb
>> loads whole database into memory, is it right? if my db size is grater
>> then my RAM how does mdb handles? do we have any configuration options to
>> set RAM allocation for mdb as i may have other applications sharing the
>> same RAM?
>>
>
> It uses RAM in accordance to the size of the database, not the maxsize.
> Generally, you set the maxsize value to something really large and forget
> about it. I would note you already have a fairly large database. However,
> MDB should use significantly *less* RAM than your old back-hdb database
> overall, because your old back-hdb DB had to use multiple caches in RAM as
> a part of the slapd process (cachesize, idlcachesize, dncachesize) in
> addition to the BDB cache (set_cachesize in DB_CONFIG).
>
> --Quanah
>
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Tuesday, October 03, 2017 11:03 AM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Quanah,
>
>
> Quick question regarding "maxsize" in mdb, slapd-mdb man page says we
> have to preallocate the db size based on future growth of your data, that
> means will it create a data.mdb of maxsize? what i read from docs is, mdb
> loads whole database into memory, is it right? if my db size is grater
> then my RAM how does mdb handles? do we have any configuration options to
> set RAM allocation for mdb as i may have other applications sharing the
> same RAM?Â
It uses RAM in accordance to the size of the database, not the maxsize.
Generally, you set the maxsize value to something really large and forget
about it. I would note you already have a fairly large database. However,
MDB should use significantly *less* RAM than your old back-hdb database
overall, because your old back-hdb DB had to use multiple caches in RAM as
a part of the slapd process (cachesize, idlcachesize, dncachesize) in
addition to the BDB cache (set_cachesize in DB_CONFIG).
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Quanah,
Quick question regarding "maxsize" in mdb, slapd-mdb man page says we have
to preallocate the db size based on future growth of your data, that means
will it create a data.mdb of maxsize? what i read from docs is, mdb loads
whole database into memory, is it right? if my db size is grater then my
RAM how does mdb handles? do we have any configuration options to set RAM
allocation for mdb as i may have other applications sharing the same RAM?
Thanks,
Ram
On Tue, Oct 3, 2017 at 8:08 AM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Monday, October 02, 2017 5:14 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
>> Thank you, would you recommend different user for replication or just use
>> the roodn? i know its upto me but just trying to follow the best
>> practices :)
>>
>
> It is generally recommended not to use the rootdn for replication.
>
>
> --Quanah
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Monday, October 02, 2017 5:14 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
>
> Thank you, would you recommend different user for replication or just use
> the roodn? i know its upto me but just trying to follow the best
> practices :)
It is generally recommended not to use the rootdn for replication.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Monday, October 02, 2017 2:20 PM -0700 "Paul B. Henson"
<henson(a)acm.org> wrote:
> On Mon, Sep 25, 2017 at 04:31:40PM +0200, OndÅ™ej KuznÃk wrote:
>
>> I'd apply it everywhere you have syncprov configured, these could send a
>> cookie with too little information for a replica to spot and skip a
>> duplicate.
>
> Hmm, I applied the patch to all four of my servers but I'm still seeing
> the errors :(...
Are you positive the servers are in sync at this point? I.e., did you
freshly reload from whatever you consider your golden master them after
applying the patch?
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Thank you, would you recommend different user for replication or just use
the roodn? i know its upto me but just trying to follow the best practices
:)
Ram
On Mon, Oct 2, 2017 at 2:38 PM, Quanah Gibson-Mount <quanah(a)symas.com>
wrote:
> --On Monday, October 02, 2017 3:30 PM -0700 rammohan ganapavarapu <
> rammohanganap(a)gmail.com> wrote:
>
>
> database config
>> # rootdn directive for config
>> rootdn "cn=admin,cn=config"
>> rootpw {SSHA}XXXXXXXXX
>>
>
> As noted in the slapd-config(5) man page, the default rootdn for cn=config
> is cn=config. I'd generally go with the default. You would need to set
> the rootpw as you've done above though. ;)
>
> I.e., I'd just do:
>
> database config
> rootpw {SSHA}XXXXXXXXXXXXXXXX
>
> And go with the default rootdn.
>
>
> --Quanah
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
>
--On Monday, October 02, 2017 3:30 PM -0700 rammohan ganapavarapu
<rammohanganap(a)gmail.com> wrote:
> database     config
># rootdn directive for config
> rootdn      "cn=admin,cn=config"
> rootpw      {SSHA}XXXXXXXXX
As noted in the slapd-config(5) man page, the default rootdn for cn=config
is cn=config. I'd generally go with the default. You would need to set
the rootpw as you've done above though. ;)
I.e., I'd just do:
database config
rootpw {SSHA}XXXXXXXXXXXXXXXX
And go with the default rootdn.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>