Run time issue after upgrading Nest.DLL [Elastic search]

Madan Shekar

Hello Folks,

I have updated to Nest.dll from 6.8.1 to 7.17.1 , after that i'm getting a runtime issue like below

Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService[104] Health check elasticsearch threw an unhandled exception after 0.5423ms System.TypeLoadException: Could not load type 'Nest.IPingResponse' from assembly 'Nest, Version=7.0.0.0, Culture=neutral, PublicKeyToken=96c599bbe3e70f5d'. at HealthChecks.Elasticsearch.ElasticsearchHealthCheck.CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken)

I have verified in the entire solution i didn't see any reference for older version , and also i did clean and rebuild and nuget cache restore.

Please help me to resolve this issue.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Bohdan Stupak4y ago
I'm usually using a low-level library for elasticsearch so I'm not an expert on this. But my guess is that ElasticClient is expected to be singleton as described in this issue https://github.com/elastic/elasticsearch-net/issues/4018 and in you app it's transient or scoped so it gets disposed
+1

Madan Shekar4y ago

Hey Bohdan,

Thakns for your inputs i will work on this.

I have one more question for you after upgrading NEST.DLL 6.8 to 7.17.1 i'm getting below runtime exception.

if (client.Indices.Exists(IndexName).Exists)

at System.Threading.SemaphoreSlim.CheckDispose()
   at System.Threading.SemaphoreSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.SemaphoreSlim.Wait(TimeSpan timeout)
   at Elasticsearch.Net.RequestPipeline.FirstPoolUsage(SemaphoreSlim semaphore)
   at Elasticsearch.Net.Transport`1.Request[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)
   at Elasticsearch.Net.ElasticLowLevelClient.DoRequest[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters)
   at Nest.ElasticClient.DoRequest[TRequest,TResponse](TRequest p, IRequestParameters parameters, Action`2 forceConfiguration)
   at Nest.NamespacedClientProxy.DoRequest[TRequest,TResponse](TRequest p, IRequestParameters parameters, Action`2 forceConfiguration)
   at Nest.Specification.IndicesApi.IndicesNamespace.Exists(IIndexExistsRequest request)
   at Nest.Specification.IndicesApi.IndicesNamespace.Exists(Indices index, Func`2 selector)

Please share your thoughts on this.

Bohdan Stupak4y ago
Failing healthcheck may suggest two options:
1. Your elasticsearch instance became unresponsive
2. Healthcheck format somehow changes between versions
You should verify both of these options. Can you query your elasticsearch instance via rest API?
+1