Comment by freakynit

6 days ago

Feels the same to me as well.

"Take snapshot and begin streaming replication"... like to where? The snapshot isn't even prepared fully yet and definitely hasn't reached the target. Where are you dumping/keeping those replication logs for the time being?

Secondly, how are you managing database state changes due to realtime update queries? They are definitely going in source table at this point.

I don't get this. Im still stuck on point 1... have read it twice already.

6 comments

freakynit

Reply
mattlord  6 days ago

It's open source. If you want to understand exactly how, you certainly can! :-)

https://github.com/vitessio/vitess

https://vitess.io/docs/reference/vreplication/

https://vitess.io/docs/reference/features/vtgate-buffering/

  • Snelius  4 days ago

    He can't. It's not a reference, just a bunch of CLI examples. Please learn what is the reference. Even docs is a BS, wonderful product. Overall this article is a typical advertising and clickbait..

    • joshuamorton  3 days ago

      The code is open source though, you can read it. The cli examples point you towards the relevant bits of the actual database code to read.

      For my own sake, I'm not sure what is so surprising here. "Turn up a hot second replica and fail over to it intentionally behind a global load balancer." Is pretty well trodden ground.

      3 replies →