# Socket timeout using the v8 driver

**URL:** <https://discuss.elastic.co/t/socket-timeout-using-the-v8-driver/321197>\
**Category:** Elasticsearch\
**Tags:** docker, language-clients\
**Created:** [December 14, 2022, 8:41am UTC](https://discuss.elastic.co/t/socket-timeout-using-the-v8-driver/321197 "2022-12-14T08:41:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mhanna\_Abu\_Tareef](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhanna_abu_tareef/32/99030_2.png) [@Mhanna\_Abu\_Tareef](https://discuss.elastic.co/u/Mhanna_Abu_Tareef)\
**Post date:** [December 14, 2022, 8:41am UTC](https://discuss.elastic.co/t/socket-timeout-using-the-v8-driver/321197/1 "2022-12-14T08:41:34Z")

</div>

Just moved to the new elastic client v8, but not able to overcome this annoying issue.  
a single request - create index - fails by timeout  
in the server log i can see the index got created

the delete index right after it, succeeded.

```auto
Caused by: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-0 [ACTIVE]
	at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:915)
	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:300)
	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:288)
	at co.elastic.clients.transport.rest_client.RestClientTransport.performRequest(RestClientTransport.java:147)
	at co.elastic.clients.elasticsearch.indices.ElasticsearchIndicesClient.create(ElasticsearchIndicesClient.java:266)
	at com.k2view.fabric.search.providers.ElasticSearchProvider.lambda$createIndex$10(ElasticSearchProvider.java:171)
	at com.k2view.fabric.search.FabricSearchException.wrap(FabricSearchException.java:28)
	... 74 more
Caused by: java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-0 [ACTIVE]
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.timeout(HttpAsyncRequestExecutor.java:387)
	at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:98)
	at org.apache.http.impl.nio.client.InternalIODispatch.onTimeout(InternalIODispatch.java:40)
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.timeout(AbstractIODispatch.java:175)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.sessionTimedOut(BaseIOReactor.java:261)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.timeoutCheck(AbstractIOReactor.java:502)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.validate(BaseIOReactor.java:211)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591)
	at java.base/java.lang.Thread.run(Thread.java:833)

```

---

<div class="post-metadata">

**Author:** ![Mhanna\_Abu\_Tareef](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mhanna_abu_tareef/32/99030_2.png) [@Mhanna\_Abu\_Tareef](https://discuss.elastic.co/u/Mhanna_Abu_Tareef)\
**Post date:** [December 15, 2022, 8:14am UTC](https://discuss.elastic.co/t/socket-timeout-using-the-v8-driver/321197/2 "2022-12-15T08:14:15Z")

</div>

It's related to a disk space issue.  
Why would you have such a feature that switched the indices to read only when disk space get to only X% space left... while actual space might be dozens of GBs...

At least, report to client a proper indication...

---

<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:** [January 12, 2023, 8:14am UTC](https://discuss.elastic.co/t/socket-timeout-using-the-v8-driver/321197/3 "2023-01-12T08:14:25Z")

</div>

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