Mateusz Kwapich 3d314761c3 introduce OperationKey ... Summary: From time to time we're experiencing the blobstore healer to crash because its SQL queries timing out. The rootcause of the problem is that the same blob_key may show up on the queue many times repeatedly and the query is trying to select all occurences. But, the original intention of blobstore healer is to act on a single put operation across all blobstores. To be able to identify which puts in the healer queue are part of the same operation we need some unique id that we'll use per such operation, let's call it OperationKey. corresponding configerator change to create db column: D20557659 NOTE: This diff has to be landed and rolled out first, before D20557700 is rolled out. I'm assuming that after some time since rolling out this diff all the rows in the production db will have proper `operation_key` value set. Reviewed By: krallin Differential Revision: D20557702 fbshipit-source-id: 404d9fdea6796b38193292d1bbd4b8cd4b5b3eb8		2020-03-24 10:07:31 -07:00
..
sqlite-blobstore-sync-queue.sql	introduce OperationKey	2020-03-24 10:07:31 -07:00