Coordinator fails to retrieve cluster state when proxy role is not assigned

Elastic Orchestration Elastic Cloud Enterprise (ECE)
1

I would like to get help with how to diagnose below issue.

I have installed Coordinator node (Coordinator and Director) and Proxy node separately.
However, when I login to admin console , it looks like below.

coordinator_error.PNG1594×737 15.6 KB

It looks like the admin console API returns 500 internal server error.

http://xxx.xxx.xxx.xxx:12300/api/v1/elasticsearch/clusters-*/_search Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Referencing the Topology plan , I have excluded the proxy on the coordinator node as below.

coordinator_error2.PNG1526×165 19.9 KB

  • runner-Manager1 is the node which error is occurring.

Is there a log which I can look at to get more insight with the error?

2

Hi @YuWatanabe

This is a known issue with Alpha4 where the API server tries to connect to the backing Elasticsearch cluster using the proxy, and assumes the proxy always resides on the initial host (in your case it's runner-Manager1).
This issue will be resolved in the upcoming beta release.

HTH
Uri

3

@uricohen

Good to here. Thanks.

4

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