Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
M4
-
None
Description
Currently we assume that, once initialized, a tserver never changes its IP or port. That's a poor assumption (eg environments like ec2, or even on-premise when a network gets renumbered).
We should introduce a "resolver" interface to map from uuid->hostport by contacting the master (the master already maintains this registry locally). Consensus needs to be able to use this interface when it has trouble connecting to its cached peer hostport info.
Attachments
Issue Links
- is duplicated by
-
KUDU-334 consensus should refresh RPC addresses from master after TS restarts
- Resolved
- is related to
-
KUDU-1620 Consensus peer proxy hostnames should be reresolved on failure
- Resolved
-
KUDU-1885 Master caches DNS name resolution forever
- Resolved
- relates to
-
KUDU-2396 Tool to edit host/port for pending config changes in the WAL after machine migration
- Open