And if you have open IndexReaders/Searchers at the same time use 3.5 as factor (because some files were already deleted from directory, but still occupy space - *nix delete on last close) :-)
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Jason Rutherglen [mailto:jason.rutherg...@gmail.com] > Sent: Monday, November 30, 2009 11:55 PM > To: java-user@lucene.apache.org > Subject: Re: Disk full while optimizing an index > > Siraj, > > You could estimate the maximum size used during optimization at 2.5 (a > sort of rough maximum) times your current index size, and not optimize > if your index (at 2.5 times) would exceed your allowable disk space. > > Jason > > On Mon, Nov 30, 2009 at 2:50 PM, Siraj Haider <si...@jobdiva.com> wrote: > > Index optimization fails if we don't have enough space on the drive and > > leaves the hard drive almost full. Is there a way not to even start > > optimization if we don't have enough space on drive? > > > > regards > > -siraj > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
