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>
Invalid NEST response built from a unsuccessful low level call on PUT: /prod/alarm/VIS0260fe00000020170405075702?refresh=true
Audit trail of this API call:
-  BadResponse: Node: https://943b40xxxxx.eu-west-1.aws.found.io:9243/ Took: 00:01:00.0149979
-  MaxTimeoutReached: Took: -736423.08:11:44.2522492
OriginalException: System.Net.WebException: The operation has timed out
at Elasticsearch.Net.HttpConnection.Request[TReturn](RequestData requestData) in C:\code\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 145
<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 stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>