Thanks for reaching back.
Perhaps it would be easier if we forget about the “Cluster” word. Let’s just say I have 3 servers running ELK, that are syncronized. My idea was to allow n8n to have a 3 server pool of options. If one was down, n8n could just use another one.
I’m more of a Python user, so I’ll use a snippet of Python to explain what I’m doing on other scripts, and that would be cool to replicate, if is possible, in n8n. Basically I’m using multiple servers, on the Elasticsearch API Client, and these servers will be contacted. This offers redundancy for the script in case one of the nodes fail. Obviously with just one node, if the node fails, any scripts running would fail due to the server being down.
es = Elasticsearch(
["https://server1:9200", "https://server2:9200", "https://server3.com:9200"],
That being said, since I have 3 ELK Servers but n8n is just using one, if something happens to that server, all the Workflows using ELK would fail. I take it by your answer that perhaps it’s not allowed to have multiple URLs on the ELK Credential configuration page. (Tried with commas, but it didn’t work).
Your sugestion is viable, however, ELK implements its own kind of Load Balancing, so it would be redundant to create another Load Balancer.
Nevertheless, it may end up being the alternative, in order to be asured that if something came up on one of the servers, n8n would still manage to execute all Workflows.