Cribl: High CPU utilization on Lakehouses
Affected components: Cribl LakeGlobal - Cribl Lake
Timeline of updates
- investigating
We are currently investigating this issue.
- investigating
We're currently investigating an issue with high CPU utilization on small Lakehouses. No customer action required at this time. If you are impacted, you will see delayed or failing searches to Lakehouse.
- investigating
Update: We have restarted the impacted Lakehouses, which is allowing them to slowly return to a normal state. There is still no Customer action required at this time. Investigating: We are still in the process of investigating a long-term resolution, and the incident is still active.
- identified
The issue has been identified and a fix is being implemented.
- monitoring
A fix has been implemented and we are monitoring the results.
- monitoring
Update: The impacted tenants have been restarted, and are being actively monitored for the impact-thresholds. We will proactively intervene if necessary, but tenants should be performing as expected. Investigating: Engineering has identified the trigger and is finalizing long-term remediation plans.
- identified
The issue has been identified and a fix is being implemented.
- identified
Cribl will be performing an Emergency Maintenance at 2pm ET and 4pm ET in order to remediate this Incident. During this time, Customers should expect small windows of slow searches from Cribl Search to Lakehouse datasets during this time. If your Lakehouse does not perform as expected after this time, please contact Cribl Support for assistance.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).