Changes / Firebolt / Engines may fail to start and stop
Firebolt: Major incident: Engines may fail to start and stop
Summary
Firebolt reported a major incident affecting engine starts and stops from 2022-01-26 13:02 UTC to 2022-01-26 16:48 UTC (3 h 45 min). Ingestion on impacted engines may also have been affected. Firebolt reported a master-cluster outage that disrupted internal services; a fix was deployed and tested before resolution.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Engines may fail to start and stop
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2022-01-26 13:02 UTC
Before: not present
After: 2022-01-26 16:48 UTC
Before: not present
After: Engines, Firebolt Components - Engines
Before: not present
After: Engines may fail to start and stop.
Before: not present
After: We are continuing to investigate this issue
Before: not present
After: The issue has been identified, and a fix is being implemented.
Before: not present
After: We are continuing to work on a fix for the issue.
Before: not present
After: The issue is identified and fix being implemented.
The issue affects only engines under US-EAST-1 region.
Before: not present
After: We are still experiencing the issue, and continuing to work on a fix.
Before: not present
After: We have fixed a portion of the issue with our engines and are now working on a complete fix.
This issue still only affects engines on US-EAST-1. Starting/Stopping engines in that region will not work until we resolve the issue. We will update you in 30 minutes or earlier if fixed.
Before: not present
After: We have identified and are deploying a fix, we believe the process should take 30minutes - 1hour and we'll update you at the 30m mark if it is still running or complete.
Before: not present
After: Our fix is still underway and looking good. We believe 15-30 more minutes until the issue is resolved. Please do not run any ingestion during this time. We will update you shortly once complete.
Before: not present
After: The fix has been deployed successfully and we are now testing it to ensure the efficacy. This should take ~10 minutes
Please note we found that any ingestion on the impacted engines during the timeframe may have been affected as well.
We are similarly testing those findings, and will update on what actions need to be taken if any.
Before: not present
After: Testing is complete and the issue is resolved. A full update on the issue is below, please note the restoration time, and let us know if you notice any residual impacts to your systems.
At approximately 1230 UTC we experienced an outage in our master cluster. Though we quickly rectified this particular issue, it had disrupted several internal services - most critically, one of our most important storage services entered an unresponsive state.
We made several attempts to regain the health of this system but in the end had to revert to a full restoration, which was successful. That restoration is timestamped at 12:07 UTC, meaning any ingestion done after that time will have been lost.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Engines may fail to start and stop (this change) Firebolt reported a major incident affecting engine starts and stops from 2022-01-26 13:02 UTC to 2022-01-26 16:48 UTC (3 h 45 min). Ingestion on impacted engines may also have been affected. Firebolt reported a master-cluster outage that disrupted internal services; a fix was deployed and tested before resolution. | Major incident |