I gave this a shot and it turns out that the number of stands was increasing quickly so I had to leave merges enabled.
On Fri, Aug 14, 2009 at 1:46 PM, Mattio Valentino<[email protected]> wrote: > We've been doing some query tuning and updating of our documents to > get some better performance. One of the issues we're running into is > that we have merges happening at the same time as > reindexing/refragmenting, so everything slows down noticeably. > > I have another wide-spread update to make (to fix my namespace issues > from an earlier email). The database has two forests and 16 stands > now (currently mid-merge) and it is not in production. Is it safe to > disable merges while my update is running and then re-enable them > after it is complete? The details in the Administrator's Guide seem > to indicate this would be okay in my scenario, but I thought I'd throw > this one out to the group. > > Thanks, > Mattio > _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
