Accessing AWS ElasticSearch Service v5.6 using Java High Level Rest Client v6.3.0


(Karthikeyan Thamilselvan) #1

I have an AWS ElasticSearch service with the version 5.6. I want to use Java - High Level Rest Client v6.3.0 to create indices and do all the crud operations. But as we know the structure of ES v5.6 and ES v6.3 are different.
Will there be any problem if I try to access v5.6 ES using the jar of version 6.3.0?


(David Pilato) #2

They are not compatible. You need to use the 5.6 version of the client.


(Karthikeyan Thamilselvan) #3

Will it work if the AWS ES version is 6.0 and Highlevel rest client jar version is 6.3.0 ?


(David Pilato) #4

Yes.

Few notes:

  • 6.3.0 has not been released yet
  • try cloud.elastic.co :wink:. also available on AWS Marketplace

(Karthikeyan Thamilselvan) #5

Hi,

I am using snapshot version of High Level Rest client (6.3.0-SNAPSHOT) now and using AWS ES v6.0. Whenvever I tried to connect the AWS using my rest client I get the below error.

java.net.ConnectException
at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:168) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:561) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:822) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:183) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:210) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:155) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348) ~[httpcore-nio-4.4.5.jar:4.4.5]
at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:192) ~[httpasyncclient-4.1.2.jar:4.1.2]
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) ~[httpasyncclient-4.1.2.jar:4.1.2]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]

Could you please help in fixing this?


(Shane Connelly) #6

FYI, the Elasticsearch engineers don't have anything to do with the AWS ES service. For example, the REST client is not tested by Elasticsearch engineers against AWS ES, etc when it's released, so there are no guarantees that really anything will work against that service. If you're having troubles with AWS ES specifically, you may want to ask on AWS's forums (or use something like Elastic Cloud, which is the Elastic-supported Cloud solution as David linked to).


(system) #7

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