Connection Issues

Incident Report for Help Scout

Postmortem

Overview

Starting around 5:54pm EDT on Monday evening, a failure with one of our search nodes caused degraded performance with the web app, the public help desk API, as well as Docs search.

Performance issues lasted for 43 minutes, up to 6:37pm EDT. During this time, the web app was down and unavailable for 9 minutes. Customers experienced slow page loads/time outs when attempting to access Help Scout, as well as failed requests to the API.

When the node failed, our search API also failed. The web app as well as Docs rely heavily on the search API, which caused the underlying performance issues with those services.

This root of the issue was tough to track down initially. To resolve the problem, we restarted the failed search node, which helped all services to recover.

What we're doing about it

We have multiple search nodes in place, but one node going down should not negatively impact other services. This isn't an issue we've encountered in the past, so we still have a more investigative work to do on our end to figure out what caused the node, along with the search API, to fail in the first place. Based on what we find, we'll take all steps necessary to prevent this issue from happening again.

Posted May 31, 2017 - 14:40 EDT

Resolved

We're closing this one out and will plan on publishing a post-mortem in the next 48 hours. Search and email queues will be catching up for the next 10-15 minutes.
Posted May 29, 2017 - 18:44 EDT

Monitoring

Connections seem stable at this point, and we're still doing some cleanup to get back to 100%.
Posted May 29, 2017 - 18:37 EDT

Update

The web application is up and down for the moment. Performance seems normal, then you'll see blank pages for a bit. We're still working to resolve a few problems on our end ... more soon.
Posted May 29, 2017 - 18:26 EDT

Identified

We've isolated the issue to an internal API, which is failing to connect to the database. Our Ops team is working to resolve it now.
Posted May 29, 2017 - 18:09 EDT

Investigating

We're experiencing elevated connection errors in the web app and are investigating now.
Posted May 29, 2017 - 17:56 EDT