search

SDKits / ExamineX

Issue tracker for ExamineX
https://examinex.online
5 stars 0 forks source link

No documents indexed during rebuild if previous process was faulted #19

Closed eriktbe closed 3 years ago

eriktbe commented 3 years ago

If an index operation was faulted the background task will not get reset so rebuilding index operations will not be processed.

Original report:

Steps to reproduce:

Expected result:

Documents are crawled and added to the index.

Actual result:

No documents are added to the index.

The following error is shown in the Umbraco logs:

Failed to parse query string at line 1, column 24. See https://aka.ms/azure-search-full-query for supported syntax.

Call Stack: Microsoft.Rest.Azure.CloudException: at Microsoft.Azure.Search.DocumentsProxyOperations+d9`1.MoveNext (Microsoft.Azure.Search.Data, Version=10.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at Microsoft.Azure.Search.DocumentsProxyOperations+d8`1.MoveNext (Microsoft.Azure.Search.Data, Version=10.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at Microsoft.Azure.Search.DocumentsOperationsExtensions+d__17.MoveNext (Microsoft.Azure.Search.Data, Version=10.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35) at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) at Microsoft.Azure.Search.DocumentsOperationsExtensions.Search (Microsoft.Azure.Search.Data, Version=10.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35) at ExamineX.AzureSearch.AzureSearchResults+C.A (ExamineX.AzureSearch, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null) at ExamineX.AzureSearch.AzureSearchResults.A (ExamineX.AzureSearch, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null)

The indexes are reporting as healthy. I can see that the indexes themselves were created in the staging search service. See attached screenshots.

SearchService ExamineManagement

Shazwazza commented 3 years ago

Hi, thanks for reporting. There have been 2 patch version releases recently. The latest one was today for version 1.1.2

Are you able to give that a try a let us know if that resolves your issue?

Shazwazza commented 3 years ago

The underlying issue was caused by the background task thread not being reset if there was a fault so any subsequent rebuilding index operations would not be processed.