Flying Sphinx incident

Database Upgrade

Notice Resolved View vendor source →

Flying Sphinx experienced a notice incident on February 28, 2016, lasting 2h 11m. The incident has been resolved; the full update timeline is below.

Started
Feb 28, 2016, 03:38 AM UTC
Resolved
Feb 28, 2016, 05:50 AM UTC
Duration
2h 11m
Detected by Pingoru
Feb 28, 2016, 03:38 AM UTC

Update timeline

  1. identified Feb 28, 2016, 03:38 AM UTC

    Due to both CVE-2015-7547 and Heroku deprecating PG 9.1, the database for the Flying Sphinx API will be upgraded over the course of the next two hours. During this time, the API will not be available (and so indexing requests will fail, as will requests to stop/start daemons) but search daemons will continue to respond to search requests uninterrupted.

  2. identified Feb 28, 2016, 04:34 AM UTC

    Upgrade continues, but the API is available again. If/when there's any further downtime, will update here accordingly.

  3. resolved Feb 28, 2016, 05:50 AM UTC

    The CVE patch is in place, but the upgrading of PostgreSQL versions is looking to take much longer (6+ hours), and will be done at another time. This incident is considered resolved.