You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/04/11 22:34:25 UTC

[jira] [Resolved] (KUDU-1033) Capability to delete & bootstrap followers that fall too far behind log

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

Mike Percy resolved KUDU-1033.
------------------------------
          Resolution: Fixed
       Fix Version/s: Public beta
    Target Version/s: Public beta  (was: GA)

Yep, this is done.

> Capability to delete & bootstrap followers that fall too far behind log
> -----------------------------------------------------------------------
>
>                 Key: KUDU-1033
>                 URL: https://issues.apache.org/jira/browse/KUDU-1033
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: consensus
>    Affects Versions: Feature Complete
>            Reporter: Mike Percy
>            Assignee: Mike Percy
>            Priority: Critical
>             Fix For: Public beta
>
>
> Adding the capability to remotely bootstrap followers that fall too far behind the log to catch up normally could be useful in certain recovery scenarios, such as where we have only one caught-up leader and one fallen-behind follower. In this scenario, it is impossible to append to the log to change the config, and the only way to automatically recover is to remotely bootstrap the fallen-behind voter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)