Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ES5 Persistence Rest Client, AWS Elasticsearch

See original GitHub issue

I have been using the following configuration for AWS Elasticsearch connection with Rest client

workflow.elasticsearch.instanceType=EXTERNAL

# Transport address to elasticsearch
workflow.elasticsearch.version=5-rest
workflow.elasticsearch.url=https://xxxx.ap-south-1.es.amazonaws.com

workflow.elasticsearch.instanceType=EXTERNAL

# Transport address to elasticsearch
workflow.elasticsearch.version=5
workflow.elasticsearch.url=https://xxxx.ap-south-1.es.amazonaws.com:443

workflow.elasticsearch.instanceType=external

# Transport address to elasticsearch
workflow.elasticsearch.version=5
workflow.elasticsearch.url=https://xxxx.ap-south-1.es.amazonaws.com:443

None of them seem to be working. All throw the following:

conductor-server_1  | Error setting up elasticsearch index
conductor-server_1  | java.io.IOException: listener timeout after waiting for [30000] ms
conductor-server_1  | 	at org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:660)
conductor-server_1  | 	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:219)
conductor-server_1  | 	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:191)
conductor-server_1  | 	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:170)
conductor-server_1  | 	at com.netflix.conductor.dao.es5.index.ElasticSearchRestDAOV5.waitForHealthyCluster(ElasticSearchRestDAOV5.java:257)
conductor-server_1  | 	at com.netflix.conductor.dao.es5.index.ElasticSearchRestDAOV5.setup(ElasticSearchRestDAOV5.java:216)
conductor-server_1  | 	at com.netflix.conductor.bootstrap.BootstrapUtil.setupIndex(BootstrapUtil.java:49)
conductor-server_1  | 	at com.netflix.conductor.bootstrap.Main.main(Main.java:50)

Any help in the above is appreciated.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

kushalhaldercommented, Apr 9, 2020

The ES status to green worked. Thanks. Closing the issue

1reaction

manan164commented, Apr 9, 2020

It should be green. Otherwise, it won’t work. It is waiting for the cluster to be green. Change this property to yellow

Top Results From Across the Web

Amazon Elasticsearch Service support for Elasticsearch 5.1

Java REST client: simple HTTP/REST Java client that works with Java 7 and handles retry on node failure, as well as, round-robin, sniffing,...

Supported operations in Amazon OpenSearch Service

The following sections show the operations that OpenSearch Service supports for each version. Topics. Notable API differences; OpenSearch version 2.3 ...

Amazon OpenSearch Service FAQs

Learn how Amazon OpenSearch Service enables search, visualization, and analysis of up to petabytes of text and unstructured data for a broad set...

Elasticsearch Service Client - AWS SDK for JavaScript v3

AWS SDK for JavaScript ElasticsearchService Client for Node.js, Browser and React Native. ... Use the Amazon Elasticsearch Configuration API to create, configure, ...

Signing HTTP requests to Amazon OpenSearch Service

For the correct client version to use, see Elasticsearch client compatibility. ... an AWS Request Signing Interceptor and/or the high-level REST client.