[
https://issues.apache.org/jira/browse/KUDU-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wong resolved KUDU-1885.
-------------------------------
Fix Version/s: 1.16.0
Assignee: Andrew Wong
Resolution: Fixed
> Master caches DNS name resolution forever
> -----------------------------------------
>
> Key: KUDU-1885
> URL: https://issues.apache.org/jira/browse/KUDU-1885
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.3.0
> Reporter: Adar Dembo
> Assignee: Andrew Wong
> Priority: Major
> Fix For: 1.16.0
>
>
> TSDescriptor::GetTSAdminProxy() and TSDescriptor::GetConsensusProxy() will
> return the same proxy instances over and over. Normally, this is a reasonable
> optimization. But suppose the IP address of the tserver changes (due to a
> DHCP lease expiring or some such). Now these methods will be returning
> unusable proxies, and there's no way to "reset" them.
> Admittedly this scenario is a little contrived: if a tserver's IP address
> suddenly changes, a bunch of other stuff will break too. The tserver will
> probably need to be restarted (since it's bound to a socket whose address no
> longer exists), and consensus may be thoroughly wrecked due to built-in
> host/port assumptions (see KUDU-418).
> An issue like this was reported by a user in Slack, who was running a master
> and tserver on the same box. The symptom was "half-open" communication
> between them: the tserver could heartbeat to the master, but the master could
> not send RPCs to the tserver.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
