Hi Michael, Thanks for your reply. I’m running it on windows. I have checked my code, I’m closing IndexWriter after adding document to it. We are not getting this issue always but it’s frequency is high in our application. Can you please provide your suggestion?
Thanks, Mukul From: Michael McCandless [mailto:luc...@mikemccandless.com] Sent: Thursday, June 16, 2016 10:22 PM To: Lucene Users <java-user@lucene.apache.org>; Mukul Ranjan <mran...@egain.com> Subject: Re: LockFactory issue observed in lucene while getting instance of indexWriter Are you running on Windows? This is not a LockFactory issue ... it's likely caused because you closed IndexWriter, and then opened a new one, before closing NRT readers you had opened from the first writer? Mike McCandless http://blog.mikemccandless.com On Thu, Jun 16, 2016 at 6:19 AM, Mukul Ranjan <mran...@egain.com<mailto:mran...@egain.com>> wrote: Hi, I'm observing below exception while getting instance of indexWriter- java.lang.IllegalArgumentException: Directory MMapDirectory@"directoryName" lockFactory=org.apache.lucene.store.NativeFSLockFactory@1ec79746<mailto:lockFactory=org.apache.lucene.store.NativeFSLockFactory@1ec79746> still has pending deleted files; cannot initialize IndexWriter Is it related to the default used NativeFSLockFactory. Should I use simpleFSLockFactory to avoid this type of issue. Please suggest as I'm getting the above exception in my application. Thanks, Mukul Visit eGain on YouTube<https://www.youtube.com/user/egainchannel> and LinkedIn<https://www.linkedin.com/company/egain-corporation>
