Hi, The index will stay on old state of the last commit. All data after the last commit is lost, the segments started will be deleted on cleanup when a new merge triggers. This is especially true for sure since Lucene 6 because it uses Java 7's atomic renames to publish commit and also fsyncs the directory.
----- Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Kudrettin Güleryüz [mailto:kudret...@gmail.com] > Sent: Thursday, May 18, 2017 5:28 PM > To: Lucene Users <java-user@lucene.apache.org> > Subject: Re: Program killed > > Sorry, I was specifically asking for the effect on Lucene index that was > being updated when the program is killed during first phase of the > two-phase commit model. Would the index be broken? Is there anything that > can be done to prevent it, how can it be fixed? Insight on this would be > great. > > Thank you > > > > On Thu, May 18, 2017 at 10:37 AM Kudrettin Güleryüz > <kudret...@gmail.com> > wrote: > > > Hi, > > > > What happens if a program is killed or if system is rebooted during first > > phase of the two-phase commit model? > > > > Thank you, > > Kudret > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
