Scrapbox incident

DB settings failed

Critical Resolved View vendor source →

Scrapbox experienced a critical incident on March 6, 2022 affecting Scrapbox Server, lasting 1h 24m. The incident has been resolved; the full update timeline is below.

Started
Mar 06, 2022, 07:17 AM UTC
Resolved
Mar 06, 2022, 08:41 AM UTC
Duration
1h 24m
Detected by Pingoru
Mar 06, 2022, 07:17 AM UTC

Affected components

Scrapbox Server

Update timeline

  1. identified Mar 06, 2022, 07:17 AM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Mar 06, 2022, 07:56 AM UTC

    DB configuration has been modified and is being deployed.

  3. monitoring Mar 06, 2022, 08:17 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 06, 2022, 08:41 AM UTC

    This incident has been resolved.

  5. postmortem Mar 06, 2022, 08:59 AM UTC

    Scrapbox was inaccessible for an hour. We apologize for the inconvenience. ## What happened We deployed two at the same time. * Code for new features * DB index creation code for use in new features A large number of processes requiring a non-existent DB index were running, and the DB hung up. ## Remediation plan Deploy the code that creates the DB index first. Then deploy the new functionality.