Thanks for the thoughts here. I do get a bit carried away sometimes,
wanting to support fringe cases. I'll go forward assuming the same port
number.
On 2015-08-12 10:27, Dmitri Zagidulin wrote:
If you know one node's HTTP listening port, you know them all -- all
the nodes are supposed to liste
If you know one node's HTTP listening port, you know them all -- all the
nodes are supposed to listen on the same ports. (Otherwise, load balancing
gets awkward, etc).
A case where different nodes in the cluster are listening on different
ports is exotic enough to not be worth supporting. (Plus, t
Is there a way via the HTTP API to get the HTTP port the other nodes on
a cluster are listening on, assuming of course that I know one of the
nodes' listening port?
I am trying to find a way to pass in connection information for one of
the nodes in a cluster to an app I am writing in Go, and then
