Thanks Danny and Geoffrey, Good to know I only need reindex once. That will save a lot of time :)
Cheers, -Steve On 21/10/2010 17:42, Danny Sokolsky wrote: > You do not need to reindex twice. Just turn reindexing off before you begin > the upgrade procedure. The procedure is roughly (see the Installation Guide > for more details): > > * make sure you have a backup of your data directory and databases > * in 3.2, turn reindexing off on all of your databases > * shut down 3.2 > * uninstall 3.2 > * install 4.0 > * start up 4.0 > * go to the Admin Interface, accept license and upgrade screens > * shut down 4.0 > * uninstall 4.0 > * install 4.1 (or 4.2 if you are upgrading to 4.2) > * start up MarkLogic > * go to the Admin Interface, accept license and upgrade screens > * go to the Admin interface and turn reindexing back on for all your database. > > -Danny > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Willis, Geoffrey > Sent: Thursday, October 21, 2010 4:48 AM > To: General Mark Logic Developer Discussion > Subject: Re: [MarkLogic Dev General] Reindex data twice when upgrading ML > from3.2 to 4.1? > > Mornin, > Last Fall, I upgraded from 3.2 to 4.1 and only reindexed our > data forests once. I left reindexing on, detached and then deleted the > config data for the data forests, performed both upgrades, and then > re-defined the data forests (I had done the reindexing previously in a > test cluster so I could go live within short order after the production > upgrades without bringing the system to it's knees for weeks). We had no > problems resulting from this upgrade method. In fact, in one of our test > environments I had a forest which wouldn't reindex in a test upgrade > from 3.2 to 4.0 without crashing the cluster, however it reindexed fine > going from 3.2 to 4.1. > > > Geoff > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Steve > Mallen > Sent: Thursday, October 21, 2010 7:24 AM > To: General Mark Logic Developer Discussion > Subject: [MarkLogic Dev General] Reindex data twice when upgrading ML > from3.2 to 4.1? > > Hi all, > > I have a quick question about the ML upgrade procedure, if anyone > knows... > > I'm about to upgrade a 3.2 database to 4.1. I realise that I must first > upgrade > to 4.0 before upgrading to 4.1, but does anyone know if I need to > reindex the > data twice for this? i.e. Is it safe for me to set reindex to false in > my > current 3.2 installation, then upgrade to 4.0 (skipping reindexing), > then > upgrade to 4.1 and only then reindex at the end (only once as a final > step)? > > I only ask because I'm worried about the amount of time 2 full reindexes > will > take (but if that's what is required, so be it!) > > Cheers, > -Steve > -- Senior Software Engineer, Semantico Limited <mailto:[email protected]> <tel:+44.1273.358239> Registered in England and Wales no. 03841410, VAT no. GB-744614334. Registered office Lees House, 21-23 Dyke Road, Brighton BN1 3FE, UK. Check out all our latest news and thinking on the Discovery blog http://blogs.semantico.com/discovery-blog/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
