When a rebalance operation fails in RUNNING state, why does the table state revert to STARTING instead of CANCELED in GBase 8a?
In GBase 8a, when a table is in the RUNNING state and a rebalance operation fails, the table state transitions to STARTING rather than CANCELED. Meanwhile, when a CANCEL REBALANCE command is issued on tables in STARTING, RUNNING, or PAUSED states, the state transitions to CANCELED.
What is the design logic behind this state machine? Why does failure not directly transition to CANCELED, but instead reverts to STARTING?