[
https://issues.apache.org/jira/browse/KUDU-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-418:
-----------------------------
Priority: Major (was: Critical)
We've been living without this for a few years so I guess it shouldn't be
considered major
> Dynamically update peer host-ports based on registration in master
> ------------------------------------------------------------------
>
> Key: KUDU-418
> URL: https://issues.apache.org/jira/browse/KUDU-418
> Project: Kudu
> Issue Type: Improvement
> Components: consensus, master
> Affects Versions: M4
> Reporter: Todd Lipcon
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
