I’ve been evaluating CrateDB and while testing the recovery features noticed that all primary shards ended up being assigned to a single node after simulating node failures:
I tried running the ALTER table command:
ALTER TABLE test_table REROUTE PROMOTE REPLICA SHARD 2 ON 'Rollspitze' WITH (accept_data_loss = FALSE) ;
and got the error:
SQLParseException[[allocate_stale_primary] primary [test_table] is already assigned]
Is this the correct approach to re-assigning the primary shard to other nodes in the cluster?