Open jeffreywescott opened 8 years ago
This is a little meta, but one could write a migration for the _migrations
table to tag replication for this table, no?
Interesting idea, @jordanh ... still, I think it would be better as a feature on this module.
What would you propose as the interface? Configuration options in database.json
and/or command line switches?
Yeah, I think something like numReplicas
and numShards
in database.json
is the way to go.
rethink-migrate seems to have no way to set the
replicas
attribute when creating the_migrations
table (see here), which means that in a real-world production environment, the_migrations
table is not being replicated across all nodes in the cluster.