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

ASF subversion and git services commented on KUDU-1620:
-------------------------------------------------------

Commit 93cd87625dcd9495a9c9769a9329492b990b3bff in kudu's branch 
refs/heads/branch-1.18.x from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=93cd87625 ]

[docs] update on master restart in quickstart docs

Since KUDU-1620 has been resolved a long time ago, there is no need
to have an extra section on limitations on restarting Kudu masters
in the quickstart docs.

Change-Id: I15c5dc0f6a06dfbbe3ef888c4f5bfe5331d221fd
Reviewed-on: http://gerrit.cloudera.org:8080/22934
Tested-by: Kudu Jenkins
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
(cherry picked from commit 8fd6d02e0f9949382be38071e28f42b6fcb67a9b)
Reviewed-on: http://gerrit.cloudera.org:8080/22937


> 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
>            Assignee: Andrew Wong
>            Priority: Major
>              Labels: docker
>             Fix For: 1.16.0
>
>
> 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
(v8.20.10#820010)

Reply via email to