Qubole incident
Degraded performance issue (cluster start/stop and command failures) on wellness.qubole.com
Qubole experienced a minor incident on May 2, 2022 affecting Command Processing and Cluster Operations, lasting 18h 55m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 02, 2022, 10:05 PM UTC
We are facing the degraded performance in wellness.qubole environment and DevOps team is investigating the issue further
- identified May 03, 2022, 03:24 AM UTC
DevOps has identified the issue with an internal component and they are implementing a fix for this to resolve the issue at the earliest.
- identified May 03, 2022, 04:10 AM UTC
DevOps has identified the issue with an internal component and they are implementing a fix for this to resolve the issue at the earliest.
- identified May 03, 2022, 01:04 PM UTC
DevOps continues to work on the resolution for the issue in the control plane for wellness.qubole environment. We should have the issue resolved within the next few hours. We will update accordingly.
- resolved May 03, 2022, 05:01 PM UTC
The degraded performance issue on wellness.qubole.com is resolved.