Feature Request: Add support for reverting Online DDL’s forced cutover

[stankevich]

Feature Description

Discussed with @shlomi-noach and @rohit-nayak-ps.

Similar to #18107.

Once a forced Online DDL cutover is initiated, it is currently not possible to stop it or revert it to a non-forced state. If it can’t complete successfully, it goes on to killing queries on every subsequent cutover attempt. It would be great to “un-force” the cutover to avoid this behavior.

Use Case(s)

Stopping a forced cutover that can’t succeed and retrying at a later time without killing queries on every attempt.

[shlomi-noach]

After further thinking, I wonder how important it is to have this assuming we do #18107? I'm still fine with doing it, but feel like #18107 would render this less of a pain.

[stankevich]

Thanks, @shlomi-noach! Yeah, if #18107 is addressed by adding support for going back to the postpone_completion state, this request is redundant. Closing.

[shlomi-noach]

#18107 closed by #18118.