Failed to optimize index: 'default'. Message: background merge hi

Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.

AI OnAI Off

Home / Forums / Developers (Main Products) Forum / CMS 7.5 - 11 /

Failed to optimize index: 'default'. Message: background merge hit exception.

Marija Jemuovic

Vote:

Hi,

I have a standard search on an Azure website and the index got corrupted. Now, I am trying to recreate the index, but it's a large site and it takes ages. Eventually, I got the following errors:

2016-06-07 16:04:31,793 [191] ERROR EPiServer.Search.RequestHandler: Update batch could not be sent to service uri 'http://xxx/indexingservice/indexingservice.svc/update/?accesskey=local'. Message: 'The operation has timed out   at System.Net.HttpWebRequest.GetResponse()
   at EPiServer.Search.RequestHandler.MakeHttpRequest(String url, NamedIndexingServiceElement namedIndexingServiceElement, String method, Stream postData, Action`1 responseHandler)
   at EPiServer.Search.RequestHandler.SendRequest(SyndicationFeed feed, String namedIndexingService, Collection`1 ids)'
2016-06-07 16:04:31,835 [191] ERROR EPiServer.Search.RequestQueueHandler: Send batch for named index 'serviceName' failed. Items are left in queue.
2016-06-07 16:04:31,793 [199] ERROR EPiServer.Search.IndexingService.IndexingService: Failed to optimize index: 'default'. Message: background merge hit exception: _2j23:C36616 _2j56:c100 into _2j57 [optimize] [mergeDocStores]
   at Lucene.Net.Index.IndexWriter.Optimize(Int32 maxNumSegments, Boolean doWait) in d:\Lucene.Net\FullRepo\trunk\src\core\Index\IndexWriter.cs:line 2773
   at Lucene.Net.Index.IndexWriter.Optimize(Boolean doWait) in d:\Lucene.Net\FullRepo\trunk\src\core\Index\IndexWriter.cs:line 2706
   at Lucene.Net.Index.IndexWriter.Optimize() in d:\Lucene.Net\FullRepo\trunk\src\core\Index\IndexWriter.cs:line 2674
   at EPiServer.Search.IndexingService.IndexingServiceHandler.OptimizeIndex(NamedIndex namedIndex)

The entire folder is 53.1 MB so far, there are 35K pages in the DB.

Any ideas?

#149783

Jun 07, 2016 16:16

Daniel Ovaska

Vote:

Remove everything in index folder, increase request timeout in IIS and try again?

<system.web>
    <httpRuntime executionTimeout="180" />
</system.web>

#149784

Jun 07, 2016 16:59

Please login to post a reply