Workaround · Self-hosting & upgrades · Blocks work
Self-hosted default SeaweedFS storage fails under concurrent writes
2 source threads · first seen 2026-08 · last seen 2026-09
Summary
The default SeaweedFS object storage in an on-prem Sentry setup kept failing under concurrent writes, so the user swapped it for Garage, which worked reliably.
- Affects
- Teams running Sentry on-prem
- Workaround
- Replaced SeaweedFS with Garage.
- Switched to or considered
- Garage
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“I had to swap out their default SeaweedFS setup for Garage because the former kept failing under concurrent writes”
“just last week I diagnosed issues with SeaweedFS failing under concurrent writes when backing Sentry and could swap it out for Garage in a day”