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/09/30 15:04:20 UTC

[jira] [Created] (KUDU-1668) Add support for aborting a config-change operation that cannot commit

Mike Percy created KUDU-1668:
--------------------------------

             Summary: 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


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)