# IOException with C# client **URL:** \ **Category:** Elasticsearch\ **Created:** [October 31, 2011, 9:58pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731 "2011-10-31T21:58:42Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Arxisos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arxisos/32/3048_2.png) [@Arxisos](https://discuss.elastic.co/u/Arxisos)\ **Post date:** [October 31, 2011, 9:58pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/1 "2011-10-31T21:58:42Z")
Hi, I'm in the progress of creating a custom C# client for elastic search with RestSharp [http://restsharp.org/](http://restsharp.org/). Everything works without a problem except searching. I'm indexing this document: { "Content": "Hello!", "User": "Arxisos" } And after that I start the search request: POST [http://http//localhost:9200/twitter/tweet/\_search](http://http//localhost:9200/twitter/tweet/_search) HTTP/1.1 Accept: application/json, application/xml, text/json, text/x-json, text/javascript, text/xml, application/json User-Agent: RestSharp 102.3.0.0 Content-Type: application/json Host: http Content-Length: 82 Accept-Encoding: gzip, deflate Proxy-Connection: Keep-Alive { "query":{ "fuzzy":{ "User":{ "value":"Arxksos", "min\_similarity":0.1 } } } } Often that works without any problem: { "took":2, "timed\_out":false, "\_shards":{ "total":5, "successful":5, "failed":0 }, "hits":{ "total":1, "max\_score":0.3068528, "hits":[ { "\_index":"twitter", "\_type":"tweet", "\_id":"1", "\_score":0.3068528, "\_source":{ "Content":"Hello!", "User":"Arxisos" } } ] } } But sometimes elasticsearch returns with an empty result: { "took":1, "timed\_out":false, "\_shards":{ "total":5, "successful":5, "failed":0 }, "hits":{ "total":0, "max\_score":null, "hits":[] } } After looking in the log file I found this: [2011-10-31 22:07:43,368][WARN][http.netty] [Projector] Caught exception while handling client http traffic, closing connection java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:321) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) The exception has a german description because my operating system's language is german. Here is the english translation: An existing connection was closed by the remote host. Do you thing the error is in my client implementation? Do I make a fault when creating the http request? I would be happy if someone can give some tips to solve this problem. Thanks for reading, Steffen ---
**Author:** ![Arxisos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arxisos/32/3048_2.png) [@Arxisos](https://discuss.elastic.co/u/Arxisos)\ **Post date:** [October 31, 2011, 10:05pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/2 "2011-10-31T22:05:32Z")
Maybe it's important that I've done this in the config file: gateway.type: none ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 1, 2011, 5:39pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/3 "2011-11-01T17:39:04Z")
Hey, Hard to tell, the failure means that the client side closed the connection. Does RestSharp opening and closing connections for each request? -shay.banon On Tue, Nov 1, 2011 at 12:05 AM, Arxisos [arxisos@googlemail.com](mailto:arxisos@googlemail.com) wrote: > Maybe it's important that I've done this in the config file: > gateway.type: none ---
**Author:** ![Arxisos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arxisos/32/3048_2.png) [@Arxisos](https://discuss.elastic.co/u/Arxisos)\ **Post date:** [November 1, 2011, 8:43pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/4 "2011-11-01T20:43:03Z")
## I implemented the http communication myself with System.Net.WebRequest. Internally RestSharp is using this class, too. The connection is closed when the instance of this class is disposed.\* \* The behavior is the same even when I switch between my implementation and RestSharp. After experimenting a few minutes I realized that this behavior only happens when I'm doing CRUD (put and delete) operations very frequently. I was calling Elasticsearch with an integration test which I executed very often, so the document was created and deleted very often per second. Maybe my fault isn't a bug, but a expected overhead of Elasticsearch to add the document to the index in the specific shard (I've got 5 shards and 1 replica). While this happens the search is returning with zero elements.\* \* Do you thing this guess is plausible? Am Dienstag, 1. November 2011 18:39:04 UTC+1 schrieb kimchy: > Hey, > > Hard to tell, the failure means that the client side closed the > connection. Does RestSharp opening and closing connections for each request? > > -shay.banon > > On Tue, Nov 1, 2011 at 12:05 AM, Arxisos [arx...@googlemail.com](mailto:arx...@googlemail.com) wrote: > > > Maybe it's important that I've done this in the config file: > > gateway.type: none ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 1, 2011, 10:08pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/5 "2011-11-01T22:08:46Z")
Is there a chance that you end up with no documents in the index, and thats why the result is empty? Otherwise, indexing / deleting data will not affect search returning no results suddenly... On Tue, Nov 1, 2011 at 10:43 PM, Arxisos [arxisos@googlemail.com](mailto:arxisos@googlemail.com) wrote: > I implemented the http communication myself with System.Net.WebRequest. > Internally RestSharp is using this class, too. The connection is closed > when the instance of this class is disposed.\* > \* > The behavior is the same even when I switch between my implementation and > RestSharp. > > * * * > > After experimenting a few minutes I realized that this behavior only > happens when I'm doing CRUD (put and delete) operations very frequently. > I was calling Elasticsearch with an integration test which I executed > very often, so the document was created and deleted very often per second. > > Maybe my fault isn't a bug, but a expected overhead of Elasticsearch to > add the document to the index in the specific shard (I've got 5 shards and > 1 replica). > While this happens the search is returning with zero elements.\* > \* > > Do you thing this guess is plausible? > > Am Dienstag, 1. November 2011 18:39:04 UTC+1 schrieb kimchy: > > > Hey, > > > > Hard to tell, the failure means that the client side closed the > > connection. Does RestSharp opening and closing connections for each request? > > > > -shay.banon > > > > On Tue, Nov 1, 2011 at 12:05 AM, Arxisos [arx...@googlemail.com](mailto:arx...@googlemail.com) wrote: > > > > > Maybe it's important that I've done this in the config file: > > > gateway.type: none ---
**Author:** ![Arxisos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arxisos/32/3048_2.png) [@Arxisos](https://discuss.elastic.co/u/Arxisos)\ **Post date:** [November 2, 2011, 8:31am UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/6 "2011-11-02T08:31:16Z")
No, I'm sure that there is a document in the index because I create a GET request before starting the search to verify if a document exists. I compared the raw request which is created by my client with a search request created by Fiddler (HTTP Web Debugging Tool). They look the same: POST [http://localhost:9200/twitter/tweet/\_search](http://localhost:9200/twitter/tweet/_search) HTTP/1.1 Host: localhost:9200 Content-Length: 82 {"query": { "fuzzy": { "User": { "value": "Arxksos", "min\_similarity": 0.1 } } } } But the response is different sometimes. That's the order of operations which I'm executing in the integration test: - PUT /twitter/tweet/1 - GET /twitter/tweet/1 (verify if document exists) - POST /twitter/tweet/\_search - POST /twitter/tweet/\_count (verify again if document exists - but count is always 1 although search returns zero) - DELETE /twitter/tweet/1 I really don't know how this failure is produced. But what I know is that all works without any problem when I don't make the DELETE request at the end. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 2, 2011, 6:36pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/7 "2011-11-02T18:36:00Z")
This probably has to do with refreshing aspect. When you index a document, its not visible immediately for search (that the near real time aspect of it). By default, the index will be "refreshed" every second to make the changes happened during that second visible for search. You can force a refresh (at least for your test) by using the refresh API: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh.html). On Wed, Nov 2, 2011 at 10:31 AM, Arxisos [arxisos@googlemail.com](mailto:arxisos@googlemail.com) wrote: > No, I'm sure that there is a document in the index because I create a GET > request before starting the search to verify if a document exists. > > I compared the raw request which is created by my client with a search > request created by Fiddler (HTTP Web Debugging Tool). They look the same: > > POST [http://localhost:9200/twitter/tweet/\_search](http://localhost:9200/twitter/tweet/_search) HTTP/1.1 > Host: localhost:9200 > Content-Length: 82 > > {"query": { "fuzzy": { "User": { "value": "Arxksos", "min\_similarity": 0.1 > } } } } > > But the response is different sometimes. > > That's the order of operations which I'm executing in the integration test: > > - PUT /twitter/tweet/1 > - GET /twitter/tweet/1 (verify if document exists) > - POST /twitter/tweet/\_search > - POST /twitter/tweet/\_count (verify again if document exists - but count > is always 1 although search returns zero) > - DELETE /twitter/tweet/1 > > I really don't know how this failure is produced. But what I know is that > all works without any problem when I don't make the DELETE request at the > end. ---
**Author:** ![Arxisos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arxisos/32/3048_2.png) [@Arxisos](https://discuss.elastic.co/u/Arxisos)\ **Post date:** [November 2, 2011, 10:11pm UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/8 "2011-11-02T22:11:04Z")
Wow, calling refresh really solved the problem 🙂 As a reward for you/community I'll publish the C# client as open source. After that there will be a .Net client with extra-cool fluent syntax and convention over configuration paradigm. \*Offtopic: Maybe you'll find the syntax sooo cool that you want to create a similar java client 😃 \* Thanks for helping! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:50am UTC](https://discuss.elastic.co/t/ioexception-with-c-client/5731/9 "2017-07-06T03:50:02Z")
Closed on July 6, 2017, 3:50am UTC