[
https://issues.apache.org/jira/browse/KUDU-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Percy resolved KUDU-1668.
------------------------------
Resolution: Duplicate
Fix Version/s: n/a
> Add support for aborting a config-change operation that cannot commit
> ---------------------------------------------------------------------
>
> Key: KUDU-1668
> URL: https://issues.apache.org/jira/browse/KUDU-1668
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Reporter: Mike Percy
> Fix For: n/a
>
>
> It would be helpful from an availability perspective to allow aborting a
> failed config-change operation.
> This requires some careful thought to determine a safe design but some
> options might include:
> * Allow a second concurrent config change operation to proceed if it reverts
> the "active" config to the "committed" config
> * If the config change fails, have the leader attempt to rev the term and
> push a new NO_OP OpId with the same log index as the config change but a new
> term.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
