1
0
Fork 0

16 Commits (cdf15c172b85920a37bff4ab0ab4d5d2d34535c6)

Author SHA1 Message Date
Philip O'Toole 38d5fc42b0 Add timeout control to GetNodeAPIAddr 3 years ago
Philip O'Toole 40eaf6be24 Typo and CHANGELOG 3 years ago
Philip O'Toole 246f7fbb65 Ensure client local hostname works 3 years ago
Philip O'Toole 9aecafedbe Cluster client resolves advertised local address
Also, improve HTTP stats.
3 years ago
Philip O'Toole d90ea2e6b1 Service Node API requests locally if possible 3 years ago
Philip O'Toole 711f6664f9 Service can return HTTP API URL 3 years ago
Philip O'Toole 1f56b5372f cluster package unit tests passing 3 years ago
Philip O'Toole 281c454fc2 Refactor into distinct cluster client type 3 years ago
Philip O'Toole 0d533dfa4c Some cleanup 3 years ago
Philip O'Toole 0c53748636 Unit test mux with TLS transport 3 years ago
Philip O'Toole 4218df64dd Start TLS testing of service 3 years ago
Philip O'Toole f2947f84c4 Basic Cluster service in place 3 years ago
Philip O'Toole e934630a58 Basic cluster RPC service 3 years ago
Philip O'Toole f57ace7da2 Broadcast Store meta via standard consensus
With this change the cluster metadata (arbitrary key-value data associated with each node) is now broadcast across the cluster using the standard consensus mechanism. Specifically the use case for this metadata is to allow all nodes know the HTTP API address of all other nodes, for the purpose of redirecting requests to the leader.

This change removed the need for multiplexing two logical connections
over the single Raft TCP connection, which greatly simplifies the
networking code generally.

Original PR https://github.com/rqlite/rqlite/pull/434
5 years ago
Philip O'Toole e376812907 Add method to Store that returns leader ID
With the advent of Raft IDs, this distinction matters.
5 years ago
Philip O Toole aef17f6a52 Listener is actually a Transport 9 years ago