Update to 5.3 application breaks


(David Karlsson) #1

I updated from 5.2 to 5.3 because I see freqent node restarts and hoped that it would help.

However the indexing part of my application broke: (with exception below)

My application is c# .NET 4.5 with NEST 5.2

When updating NEST to 5.3 it now works. However I would like to understand why there where breaking changes in the 5.2->5.3 update that required me to update all applications.

<EDIT: Inserted a cleaned up exception>
Exception:
Invalid NEST response built from a unsuccessful low level call on PUT: /prod/alarm/VIS0260fe00000020170405075702?refresh=true

Audit trail of this API call:

OriginalException: System.Net.WebException: The operation has timed out

at System.Net.HttpWebRequest.GetResponse()
at Elasticsearch.Net.HttpConnection.Request[TReturn](RequestData requestData) in C:\code\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 145

Request:

<Request stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>

Response:

<Response stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>


(Ben Osborne) #2

Moved to Elasticsearch - Nest client request


(system) #3

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.


(Mark Walkom) #4

(system) #5