Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
1
-
Not defined
Description
Brief summary of the bug. What is it ? Where is it ?
Since the update to the elastic client 7.16.3 Optimize is not trying to reconnect to elasticsearch if an initial connection to it failed.
Steps to reproduce:
Run Optimize when Elasticsearch is not yet reachable, wait for a connect exception and then actually start Elasticsearch.
Actual result:
Optimize does not retry to connect, no new logs entries are produced:
Caused by: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:257) at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:244) at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:75) at org.elasticsearch.client.RestHighLevelClient.performClientRequest(RestHighLevelClient.java:2692) ... 87 more Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:174) at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:148) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) at java.base/java.lang.Thread.run(Thread.java:829)
Expected result:
Optimize should retry to connect to eventually succeed