On Thu, Jun 25, 2015 at 4:49 AM, Ezsra McDonald <[email protected]> wrote:
> So, after some testing we are planning to import to one of the four master > with replication disabled. We will then stop the instance, tar up and > distribute the partition folder to the other three nodes. > > just make sure you don't copy the ou=config and ou=system partitions to the other nodes > Thanks for the help. > > On Mon, Jun 15, 2015 at 9:49 PM, Kiran Ayyagari <[email protected]> > wrote: > > > On Tue, Jun 16, 2015 at 5:49 AM, Ezsra McDonald < > [email protected]> > > wrote: > > > > > Carlo, > > > Yes, Excellent suggestion Carlo! That did the trick. > > > > > > Now, I have a total of four servers in the Multi-Master setup, nodes A > > and > > > B in data center 1 and nodes C and D in data center 2. > > > > > > If I ldapadd to node A and only have replication enabled with node B I > > get > > > 4500 entries per minute. When I add nodes C and D to the replication I > > get > > > 1800 entries per minute. > > > > > > What is involved if I wanted to copy the data files after the import > from > > > node A to nodes C and D? Do I just tar up the related partition folder > > from > > > node A and untar it on nodes C and D? Or, is there more involved? What > is > > > the procedure? > > > > > stop the server before copying and exclude system and config partitions > > while copying > > > > > > > > > > > > > > On Mon, Jun 15, 2015 at 9:35 AM, <[email protected]> wrote: > > > > > > > Not sure how you have this set, but for our initial import we set the > > > > following property: > > > > > > > > ads-partitionsynconwrite: FALSE > > > > > > > > This property is found where you define your partition. > > > > dn: > > > > > > > > > > ads-partitionId=mypartition,ou=partitions,ads-directoryServiceId=default,ou=config > > > > > > > > Setting this false allowed us to import ~80K entries in about 15-20 > > > mins. > > > > > > > > Also, if you're using password policies, we disabled those too for > the > > > > initial import. > > > > > > > > Good Luck. > > > > > > > > > > > > -----Original Message----- > > > > From: Ezsra McDonald [mailto:[email protected]] > > > > Sent: Saturday, June 13, 2015 5:16 PM > > > > To: users > > > > Subject: Re: ApacheDS Import via CLI > > > > > > > > Having the server down for the initial import is not a problem. > > > > > > > > I am able to load 650 - 700 entries a minute. With almost 340k > entries > > to > > > > import this will take too long. My estimate is approximate 8.5 hours. > > > > > > > > I tried breaking the import into four files and executing four > ldapadds > > > > simultaneously but that does not improve the load rate. I really did > > not > > > > expect the import would be faster but I am desperate to get the > > migration > > > > done in less than three hours. > > > > > > > > This is just informational. I really don't expect there are any > > solutions > > > > to meet my desired 3 hour window. > > > > > > > > Thanks for the assistance. I will inform my team of my findings. > > > > > > > > > > > > On Fri, Jun 12, 2015 at 10:29 PM, Emmanuel Lécharny < > > [email protected] > > > > > > > > wrote: > > > > > > > > > Le 12/06/15 23:18, Ezsra McDonald a écrit : > > > > > > The OpenLDAP ldapadd utility works. I wish there was a direct > load > > > > > > kind > > > > > of > > > > > > utility like slapadd. Ldapadd is slow but studio is slower. > > > > > > > > > > Everything that inject data into a live server will be slow. > > > > > > > > > > In the near future, we will have a bulk import tool that will be > way > > > > > faster, but it will require the server to be down. > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Kiran Ayyagari > > http://keydap.com > > > -- Kiran Ayyagari http://keydap.com
