Database slowness
Incident Report for InEvent

Our servers use an asynchronous event-driven approach, rather than threads, to handle requests. With the modular event-driven architecture, we can have a bucket overflow that outputs the requests as soon as they arrive. Once these requests arrive, we perform same safe-checking and then redirect them to the appropriate logical application. This can be done in multiple ways.

What we realized during today operations was that the servers were not able to pipe these many requests as quickly as possible to the application layer. The socket was not able to quickly send the requests to the database, process the output and return to the user.

To fix this issue we are improving our load balancer, changing our socket configurations and also changing the database processing mechanism, so the queries can be processed without any additional allocation overload.

Posted Aug 26, 2020 - 15:15 EDT

This incident has been resolved.
Posted Aug 26, 2020 - 14:33 EDT
A fix has been implemented and we are monitoring the results.
Posted Aug 26, 2020 - 10:59 EDT
We are continuing to investigate this issue.
Posted Aug 26, 2020 - 08:43 EDT
We are currently investigating this issue.
Posted Aug 26, 2020 - 08:05 EDT
This incident affected: API.