mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-20 00:20:47 +00:00
bc8109f1a4
Make the table populator migration-aware. If a table is migrating to tablets, switch from normal resharding to vnode-based resharding. Vnode-based resharding requires passing a vector of "owned ranges" upon which resharding will segregate the SSTables. Compute it from the tablet map. We could also compute them from the vnodes, since tablets are identical to vnodes during the migration, but in the future we may switch to a different model (multiple tablets per vnode). Let the distributed loader decide if a table is migrating or not and communicate that to the table populator. A table is migrating if the keyspace replication strategy uses vnodes but the table replication strategy uses tablets. Currently, tables cannot enter this "migrating" state; support for this will be introduced in the next patches. Signed-off-by: Nikos Dragazis <nikolaos.dragazis@scylladb.com>