2 ms·
I am just wondering if this is Vitess related. I am moving tens of PBs into Vitess and it would be really bad if these incidents are vitess related...
by jakon89 5y ago
I am just wondering if this is Vitess related. I am moving tens of PBs into Vitess and it would be really bad if these incidents are vitess related...
- foxknox 5y agoI know a lot of GitHubbers and they say the irony is that this is one of the only clusters that is not on Vitess.
- 0xbadcafebee 5y agoI mean, you can rest assured that you will have problems with Vitess at some point. All software is buggy, and there is no guarantee one of those bugs won't be catastrophic. You should plan for a method to completely replace your entire production cluster in the event of failure. This can be quite difficult with horizontally-scaled databases. It's also not uncommon to hit a scaling limit for which there's no simple solution, or not be able to build out a replacement production cluster due to unplanned-for limitations.