Elasticsearch as a source connection fails

Connector Questions & Issues
1

Hi all,

we are trying to use Elasticsearch as a source. We are not able to connect. Through postman with the same connection settings Elasticsearch replies smoothly. Our Airbyte version is 0.40.32. Elasticsearch version 8.6.0. The log file is this …

Thank you
Costas

The connection tests failed.

failed to ping elasticsearch

Connection test logs
2023-03-24 14:08:22 INFO i.a.w.t.TemporalAttemptExecution(get):136 - Docker volume job log path: /tmp/workspace/899b9c27-efeb-492b-af65-703774969ad6/0/logs.log
2023-03-24 14:08:22 INFO i.a.w.t.TemporalAttemptExecution(get):141 - Executing worker wrapper. Airbyte version: 0.40.32
2023-03-24 14:08:22 INFO i.a.a.c.AirbyteApiClient(retryWithJitter):172 - Attempt 0 to save workflow id for cancellation
2023-03-24 14:08:22 INFO i.a.c.i.LineGobbler(voidCall):114 -
2023-03-24 14:08:22 INFO i.a.c.i.LineGobbler(voidCall):114 - ----- START CHECK -----
2023-03-24 14:08:22 INFO i.a.c.i.LineGobbler(voidCall):114 -
2023-03-24 14:08:22 INFO i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/source-elasticsearch:0.1.1 exists…
2023-03-24 14:08:22 INFO i.a.c.i.LineGobbler(voidCall):114 - airbyte/source-elasticsearch:0.1.1 was found locally.
2023-03-24 14:08:22 INFO i.a.w.p.DockerProcessFactory(create):125 - Creating docker container = source-elasticsearch-check-899b9c27-efeb-492b-af65-703774969ad6-0-pvwvw with resources io.airbyte.config.ResourceRequirements@5b196159[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=] and allowedHosts null
2023-03-24 14:08:22 INFO i.a.w.p.DockerProcessFactory(create):170 - Preparing command: docker run --rm --init -i -w /data/899b9c27-efeb-492b-af65-703774969ad6/0 --log-driver none --name source-elasticsearch-check-899b9c27-efeb-492b-af65-703774969ad6-0-pvwvw --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE= -e APPLY_FIELD_SELECTION=false -e WORKER_CONNECTOR_IMAGE=airbyte/source-elasticsearch:0.1.1 -e WORKER_JOB_ATTEMPT=0 -e AUTO_DETECT_SCHEMA=true -e AIRBYTE_VERSION=0.40.32 -e WORKER_JOB_ID=899b9c27-efeb-492b-af65-703774969ad6 airbyte/source-elasticsearch:0.1.1 check --config source_config.json
2023-03-24 14:08:22 INFO i.a.w.i.VersionedAirbyteStreamFactory(create):107 - Reading messages from protocol version 0.2.0, messages will be upgraded to protocol version 1.0.0
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - starting Source: class io.airbyte.integrations.source.elasticsearch.ElasticsearchSource
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - integration args: {check=null, config=source_config.json}
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Running integration: io.airbyte.integrations.source.elasticsearch.ElasticsearchSource
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Command: CHECK
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Integration config: IntegrationConfig{command=CHECK, configPath=‘source_config.json’, catalogPath=‘null’, statePath=‘null’}
2023-03-24 14:08:24 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):164 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - creating ElasticsearchConnection: http://000.000.0.000:9200
2023-03-24 14:08:24 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - checking elasticsearch connection
2023-03-24 14:08:26 ERROR i.a.w.i.DefaultAirbyteStreamFactory(internalLog):163 - RestClient failure: [host=http://000.000.0.000:9200]
2023-03-24 14:08:26 ERROR i.a.w.i.DefaultAirbyteStreamFactory(internalLog):163 - unknown exception while pinging elasticsearch server
Stack Trace: java.net.ConnectException: Timeout connecting to [/000.000.0.000:9200]
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:881)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:283)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:270)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1621)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1606)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1573)
at org.elasticsearch.client.RestHighLevelClient.info(RestHighLevelClient.java:774)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchConnection.checkConnection(ElasticsearchConnection.java:101)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchSource.check(ElasticsearchSource.java:51)
at io.airbyte.integrations.base.IntegrationRunner.runInternal(IntegrationRunner.java:125)
at io.airbyte.integrations.base.IntegrationRunner.run(IntegrationRunner.java:100)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchSource.main(ElasticsearchSource.java:34)
Caused by: java.net.ConnectException: Timeout connecting to [/000.000.0.000:9200]
at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169)
at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:628)
at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:894)
at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:184)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:214)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:158)
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:833)
2023-03-24 14:08:26 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Completed integration: io.airbyte.integrations.source.elasticsearch.ElasticsearchSource
2023-03-24 14:08:26 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - completed Source: class io.airbyte.integrations.source.elasticsearch.ElasticsearchSource
2023-03-24 14:08:26 INFO i.a.w.g.DefaultCheckConnectionWorker(run):114 - Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@1081955b[status=failed,message=failed to ping elasticsearch]
2023-03-24 14:08:26 INFO i.a.w.t.TemporalAttemptExecution(get):163 - Stopping cancellation check scheduling…
2023-03-24 14:08:26 INFO i.a.c.i.LineGobbler(voidCall):114 -
2023-03-24 14:08:26 INFO i.a.c.i.LineGobbler(voidCall):114 - ----- END CHECK -----
2023-03-24 14:08:26 INFO i.a.c.i.LineGobbler(voidCall):114 -

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team