You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A second possible improvement that this issue highlights is that for draining nodes in general it would likely be optimal to do them one-by-one (even when draining them all at once).
citus_drain_node
tries to move data from multiple workers which have theirshouldhaveshards
value set to false.this behavior is similar to
rebalance_table_shards(drain_only: true)
.However, user explicitly wants to drain a single node, operation should be limited to that node only.
Scenario is
Our documentation at https://docs.citusdata.com/en/v11.0/develop/api_udf.html#citus-drain-node does not mention this behavior, even hints that it moves data out from a specified (aka single) worker. However reality is different.
The text was updated successfully, but these errors were encountered: