I’ve been trying to wire up Temporal 1.9.2 to use AWS Elasticsearch 7.7. My ES cluster is up and healthy, 9 total nodes, 3 dedicated masters, plenty of headroom it seems. In my Temporal Helm chart, I have elasticsearch: enabled: false external: true host: "my-url-redacted.com" port: "443"…

Did you curled those commands after index was autocreated? If yes, it doesn’t affect existing index. So you need to delete existing index, create template, and then create index manually. After that it should work. I would also suggest you to disable index autocreation . Btw, we released 1.11 yester…

Thanks for the reply. Yes, had done it after the index autocreated - but also tried deleting and recreating. But it was always getting overwritten by the auto-creator back to the incorrectly formatted index. Either way, yes, I am moving ahead with 1.11.1 upgrade now and then will try rewiring up …

Temporal 1.9.2 not working with Elasticsearch 7.7 - Error 400 All Shards Failed

Community Support

Upgrader July 20, 2021, 5:33pm 2

Sounds like the same situation as this thread - so I manually curled like this. The index looks correct now, I see 200’s from my ES console in AWS. However the UI still returns the same shard error even though all looks well.

Topic		Replies	Views
[Error in UI]13 INTERNAL: ListClosedWorkflowExecutions failed. Error: elastic: Error 503 (Service Unavailable): all shards failed Community Support elasticsearch , mysql , database	5	1399	June 11, 2021
Elasticsearch error for visibilitye Community Support elasticsearch	12	3264	May 3, 2021
visibilityMetricsClient exceptions in temporal-frontend pod Community Support elasticsearch , metrics , advanced_visibility , visibility , kubernetes	7	1017	April 28, 2021
Elasticsearch shard is shut down Community Support elasticsearch	0	222	February 1, 2024
Operation not support. Please use on ElasticSearch Community Support java-sdk	5	1646	June 23, 2022

Temporal 1.9.2 not working with Elasticsearch 7.7 - Error 400 All Shards Failed

Related topics