3 ms·
I might be wrong here, but can someone comment on the process required to add additional nodes on Vitess? Every time I start reading about Vitess, I fall into
by Nican 6y ago
I might be wrong here, but can someone comment on the process required to add additional nodes on Vitess?
Every time I start reading about Vitess, I fall into a hole about manual resharding, hosting multiple vitess instances per host (I think 250GB of storage each?), and that cross-shard reads may be inconsistent.
I am taking a quick look at the documentation of TiDB, and they have automatic data re-balancing, 2PC Raft-based-transactions, global snapshot isolation, and actually some nice dashboards to analyze cluster health.
Vitess just does not seem nice from an operations perspective.
- qaq 6y agoMy understanding you will have to reshard. It's always a set of tradeoffs for the most part automatic in this context will mean network and other types of overhead.
- hilbertseries 6y agoYes, if you want to add a node you have to manually reshard. It’s quite the process. I’d add each node is a MySQL database and you can make each shard as large you want. The data on different vitess shards is disjoint, so I don’t know how much you need to worry about consistency for cross shard reads. And vitess doesn’t really support cross shard transactions either.