[jira] [Commented] (KUDU-418) Dynamically update peer host-ports based on registration in master

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188431#comment-15188431 ] 

Todd Lipcon commented on KUDU-418:
----------------------------------

We also seem to have a bug in the client here where we update the address list of a tablet server, but we don't invalidate its RPC proxy, and thus we never start talking to the new TS.

> 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
>            Priority: Critical
>
> 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.4#6332)