Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insufficient level of logging in ElasticSearch IndexingBackgroundTask #16561

Closed
AndreySurkov opened this issue Aug 14, 2024 · 0 comments · Fixed by #16564
Closed

Insufficient level of logging in ElasticSearch IndexingBackgroundTask #16561

AndreySurkov opened this issue Aug 14, 2024 · 0 comments · Fixed by #16564
Labels

Comments

@AndreySurkov
Copy link
Contributor

Describe the bug

I have an instance of OrchardCore with enabled ElasticSearch indexing and IndexingBackgroundTask.
Several times per day I see in logs following error

"message":"Error while processing background task '\"OrchardCore.Search.Elasticsearch.Core.Services.IndexingBackgroundTask\"' on tenant '\"Default\"'.",

"exception":"System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at OrchardCore.Search.Elasticsearch.Core.Services.ElasticIndexManager.GetLastTaskId(String indexName)
   at OrchardCore.Search.Elasticsearch.Core.Services.ElasticIndexingService.ProcessContentItemsAsync(String indexName)
   at OrchardCore.Modules.ModularBackgroundService.<>c__DisplayClass11_2.<<RunAsync>b__1>d.MoveNext()",

"task_name":"OrchardCore.Search.Elasticsearch.Core.Services.IndexingBackgroundTask"

Of course it can be something with my instance of Elasticsearch but current level of logging does not allow to make some further investigation.

Orchard Core version

1.8.2

Expected behavior

I expect to see error details from ElasticSearch request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant