Yeah, Thrift as RPC framework. Most DB junk happens in the big pile of Hack+PHP that is the Facebook app, or at least it did in 2020, but apparently someone wrote a Thrift endpoint to munge the database from remote services too.
Some batch job (incorrectly?) deactivated certain sessions for whatever reason?
Getting "someone ran a one off job or migration that didn't do the right thing" vibes.
For instance, they could have tried implementing a "deactivate recovery phone numbers if this dataset from cell providers show the owner changed" that went wrong
* Some engineer is testing backup/restore of account data, and is running it against production and didn't realise that restoring certain info has side effects of sending out notifications.
69 comments
[ 2.9 ms ] story [ 162 ms ] threadhttps://stackoverflow.com/questions/69881980/accessing-faceb...
Getting "someone ran a one off job or migration that didn't do the right thing" vibes.
For instance, they could have tried implementing a "deactivate recovery phone numbers if this dataset from cell providers show the owner changed" that went wrong
* Some engineer is testing backup/restore of account data, and is running it against production and didn't realise that restoring certain info has side effects of sending out notifications.