phorge-phorge/resources/sql/autopatches/20180322.lock.01.identifier.sql at 9c684c80d63d08194c6d1d175a64e8f91ec07f84 - revi-archive/phorge-phorge - SiliconForest Atelier

revi-archive/phorge-phorge

mirror of https://we.phorge.it/source/phorge.git synced 2024-11-26 00:32:42 +01:00

epriestley 69bff489d4 Generate a random unique "Request ID" for SSH requests so processes can coordinate better

Summary:
Depends on D19247. Ref T13109. When we receive an SSH request, generate a random unique ID for the request. Then thread it down through the process tree.

The immediate goal is to let the `ssh-exec` process coordinate with `commit-hook` process and log information about read and write lock wait times. Today, there's no way for `ssh-exec` to interact with the `PushEvent`, but this is the most helpful place to store this data for users.

Test Plan: Made pushes, saw the `PushEvent` table populate with a random request ID. Exported data and saw the ID preserved in the export.

Maniphest Tasks: T13109

Differential Revision: https://secure.phabricator.com/D19249

2018-03-22 13:44:30 -07:00

5 lines

206 B

SQL

Raw Blame History

 ALTER TABLE {$NAMESPACE}_repository.repository_pushevent
   ADD requestIdentifier VARBINARY(12);
 ALTER TABLE {$NAMESPACE}_repository.repository_pushevent
   ADD UNIQUE KEY `key_request` (requestIdentifier);