Starburst Galaxy incident
Possible incorrect results when Galaxy Result Set Caching is enabled
Resolved after 3 days 2 hours, affecting Starburst Galaxy UI, on March 13, 2025.
The fix has been deployed to production and we're monitoring the situation
Affected components
Update timeline
- investigating Mar 13, 2025, 12:08 AM UTC
We are currently investigating a bug where query results are empty when result set caching is enabled on a cluster. This seems to affect certain catalog types, but not all. The team is investigating the root cause, but in the meantime if you're affected by this, please disable result set caching on your clusters.
- identified Mar 13, 2025, 06:08 PM UTC
The issue has been identified. There was a bug with how results are serialized to the result set cache, which threw an exception that was not handled correctly. The team is working on a fix to handle the error case.
- identified Mar 14, 2025, 12:29 AM UTC
The fix is almost ready - we expect to deploy it to production late Friday (Mar 14th).
- monitoring Mar 15, 2025, 01:03 AM UTC
The fix has been deployed to production and we're monitoring the situation
- resolved Mar 16, 2025, 03:05 AM UTC
This has been resolved
Your product runs on more than Starburst Galaxy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services