You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2016/09/15 23:54:20 UTC
[jira] [Created] (KUDU-1620) Consensus peer proxy hostnames should
be reresolved on failure
Adar Dembo created KUDU-1620:
--------------------------------
Summary: Consensus peer proxy hostnames should be reresolved on failure
Key: KUDU-1620
URL: https://issues.apache.org/jira/browse/KUDU-1620
Project: Kudu
Issue Type: Bug
Components: consensus
Affects Versions: 1.0.0
Reporter: Adar Dembo
Noticed this while documenting the workflow to replace a dead master, which currently bypasses Raft config changes in favor of having the replacement master "masquerade" as the dead master via DNS changes.
Internally we never rebuild consensus peer proxies in the event of network failure; we assume that the peer will return at the same location. Nominally this is reasonable; allowing peers to change host/port information on the fly is tricky and has yet to be implemented. But, we should at least retry the DNS resolution; not doing so forces the workflow to include steps to restart the existing masters, which creates a (small) availability outage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)