ChangesCriblHigh CPU utilization on Lakehouses
Cribl: Major incident: High CPU utilization on Lakehouses
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Cribl removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: High CPU utilization on Lakehouses
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-06-23 18:24 UTC
Before: not present
After: 2025-06-26 18:29 UTC
Before: not present
After: Cribl Lake, Global - Cribl Lake
Before: not present
After: We are currently investigating this issue.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: The issue has been identified and a fix is being implemented.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: 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.
Before: not present
After: The issue has been identified and a fix is being implemented.
Before: not present
After: 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.
Before: not present
After: A fix has been implemented and we are monitoring the results.
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
Monday, June 23, 2025
1 incident change
- MajorMajor incident
High CPU utilization on Lakehousesthis change