Card #371 · Elastic (Elasticsearch / Kibana)
Snapshot failures and restore errors in S3 and CIFS repositories
Merchants are experiencing critical failures with Elasticsearch snapshots, including restore failures due to missing blob objects in S3 and creation failures on CIFS mounts after upgrading to version 9.4.0. Some users report that snapshots are visible in the repository but cannot be restored, while others face compatibility issues with S3-compatible storage.
Pain score
0.22/ 1.00 · weighted product of four components
Reach0.82distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.74upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
the snapshot is still present in the object that lists all the available snapshots, but it's been damaged and this blob, on which it depends, is missing.
Since upgrading to 9.4.0, we are experiencing snapshot failures on our CIFS-mounted shared repository.
we are getting "s3_exception: A header you provided implies functionality that is not implemented. (Service: S3, Status Code: 501, Request ID: 286BE1B0D952065D)
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro