jivid
If Tom and/or Shlomi are reading this: you mention taking multiple logical backups per day. What benefit does this bring versus just having one per day and doing a point-in-time restore using binlogs? Is this just a tradeoff between time taken for a restore and storage you're willing to dedicate to backups?
Disclaimer: I work on Facebook's MySQL backup and restore system (https://code.facebook.com/posts/1007323976059780/continuous-...)
We use it because it works well for us. We've put a lot of work into making MySQL scale for us to the point where it's a very well supported system and one of the main choices for a lot of storage decisions.
We even use MySQL as a queue for Facebook Messenger. More details about this:
https://www.youtube.com/watch?v=eADBCKKf8PA
https://code.facebook.com/posts/820258981365363/building-mob...
Remember we're backing up each database separately though, not the entire MySQL instance at once. Each database's backup is in a separate file.
We also implemented table checksums inside of mysqldump, allowing us to dump out the restored data and compare checksums as well, if required. https://github.com/facebook/mysql-5.6/commit/54acbbf915935a0...
We always diff against the same base and have 5 days in between subsequent full dumps. The number of days just comes from a trade off between space occupied by the backups and time it takes to generate them.
> Is there no better way to handling this than polling?
There's definitely different ways to approach this, we find polling works well for us. We also use the same database for crash recovery, so doing the assignments through it serves both purposes.
> Presumably you can only get this parallelism by disabling FK integrity. Is it re-enabled in the following VERIFY stage?
I'm not sure what you mean by parallelism through disabling FK integrity. Splitting the backup into its tables means we can restore a subset of tables instead of the entire backup. This allows us to load individual tables concurrently, but also not have to wait to load a massive database if all we need is a few small tables.
https://code.facebook.com/posts/1040181199381023/python-in-p...
Origami – Design prototyping app by Facebook
Whatsapp Hits 1B monthly active users
EdgeDB – The next generation object database
Instagram releases new app for mini video loops
Building 360 Video
What a $40 Video Has to Do with Becoming a Tech Unicorn
Looking at their other repos and the addresses you linked to, looks like the project for publishing the changes is at https://github.com/hatnote/wikimon, which is in turn getting changes from an IRC feed at https://meta.wikimedia.org/wiki/Research:Data#IRC_Feeds
EDIT: Should be working now
So to directly address your concern, you can't download the keypair at any point in time, it's just a one time thing. To me that seems much more secure than emailing out a root password and enabling password authentication by default.
As for what would happen if they did group by company? I'm guessing that Google would be #1 pretty much everywhere, save maybe Russia and China.