Lucene.Net.Index.MergePolicy+MergeException

Chantale Laberge asked on February 6, 2015 18:37

For everyone's benefit, yesterday we came to this problem, after migrating all contents from a DEV machine to a PROD machine:

Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Lucene.Net.Index.MergePolicy+MergeException
Stack:
   at Lucene.Net.Index.ConcurrentMergeScheduler.HandleMergeException(System.Exception)
   at Lucene.Net.Index.ConcurrentMergeScheduler+MergeThread.Run()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

After reindexing the search indexes on PROD again, the error was gone

Correct Answer

Jason S answered on June 4, 2015 14:45

I ran into this on a site yesterday. For those who may encounter the issue and need to know where to delete the SmartSearch index, it can be found:

\CMS\App_Data\CMSModules\SmartSearch

There will be a folder there that matches your corresponding index name.

Jason

0 votesVote for this answer Unmark Correct answer

Recent Answers


Roman Koníček answered on February 26, 2015 12:55 (last edited on August 9, 2016 10:34)

Hello Juan,

Thanks for sharing the solution with the community. I just would like to add that this issue is related to Lucene itself. For example you can find the links below dealing with the same issue:

https://our.umbraco.org/forum/core/general/14597-website-migration

http://developmentsitecore.blogspot.cz/2014/11/exception-info-lucenenetindexmergepolic.html

The suggestions were: "Fix: I had to actually delete the index files and re-index everything and that seems to have worked." and "Based on your errors I would double and triple check permissions and application pool is integrated and .net 4."

Best regards, Roman Konicek

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.