You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Bankim Bhavsar (Jira)" <ji...@apache.org> on 2020/09/03 22:56:00 UTC

[jira] [Resolved] (KUDU-3182) 'last_known_addr' is not specified for single master Raft configuration

     [ https://issues.apache.org/jira/browse/KUDU-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bankim Bhavsar resolved KUDU-3182.
----------------------------------
    Fix Version/s: 1.14.0
       Resolution: Fixed

Branch for 1.13 release was cut recently, so this fix will be available in the next 1.14 release.

> 'last_known_addr' is not specified for single master Raft configuration
> -----------------------------------------------------------------------
>
>                 Key: KUDU-3182
>                 URL: https://issues.apache.org/jira/browse/KUDU-3182
>             Project: Kudu
>          Issue Type: Task
>          Components: consensus, master
>            Reporter: Bankim Bhavsar
>            Assignee: Bankim Bhavsar
>            Priority: Major
>             Fix For: 1.14.0
>
>
> 'last_known_addr' field is not persisted for a single master Raft
> configuration. This is okay as long as we have a single master
> configuration. On dynamically transitioning from single master
> to two master configuration, ChangeConfig() request to ADD_PEER
> fails the validation in VerifyRaftConfig().



--
This message was sent by Atlassian Jira
(v8.3.4#803005)