# Update to 5.3 application breaks

**URL:** <https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275>\
**Category:** Elasticsearch\
**Created:** [April 5, 2017, 8:44am UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275 "2017-04-05T08:44:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Karlsson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david_karlsson/32/17091_2.png) [@David\_Karlsson](https://discuss.elastic.co/u/David_Karlsson)\
**Post date:** [April 5, 2017, 8:44am UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275/1 "2017-04-05T08:44:37Z")

</div>

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:

- [1] BadResponse: Node: [https://943b40xxxxx.eu-west-1.aws.found.io:9243/](https://943b40xxxxx.eu-west-1.aws.found.io:9243/) Took: 00:01:00.0149979
- [2] MaxTimeoutReached: Took: -736423.08:11:44.2522492

# 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](http://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.\>

---

<div class="post-metadata">

**Author:** ![BenOsborne](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benosborne/32/5686_2.png) [@BenOsborne](https://discuss.elastic.co/u/BenOsborne)\
**Post date:** [April 5, 2017, 10:48pm UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275/2 "2017-04-05T22:48:30Z")

</div>

Moved to Elasticsearch - Nest client request

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 8, 2017, 10:48pm UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275/3 "2017-04-08T22:48:32Z")

</div>

Closed on April 8, 2017, 10:48pm UTC

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

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 8, 2017, 11:34pm UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275/4 "2017-04-08T23:34:15Z")

</div>

Opened on April 8, 2017, 11:34pm UTC



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 10:01pm UTC](https://discuss.elastic.co/t/update-to-5-3-application-breaks/81275/5 "2017-07-05T22:01:20Z")

</div>

Closed on July 5, 2017, 10:01pm UTC