# Notice: S3 Gateway Critical Bug

**URL:** <https://discuss.elastic.co/t/notice-s3-gateway-critical-bug/3215>\
**Category:** Elasticsearch\
**Created:** [August 13, 2010, 11:15am UTC](https://discuss.elastic.co/t/notice-s3-gateway-critical-bug/3215 "2010-08-13T11:15:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 13, 2010, 11:15am UTC](https://discuss.elastic.co/t/notice-s3-gateway-critical-bug/3215/1 "2010-08-13T11:15:47Z")

</div>

Hi users,

If you follow the mailing list, you will see that a critical bug was  
found in the s3 gateway and the recovery process. It basically boils down to  
gateway chunking of big files (which is needed in s3) and a bug in the  
recovery process of chunked files (note, there is no bug in the snapshotting  
process). This is evident in the s3 gateway as it is chunked by default.

There is already a fix for this in master, and I will release 0.9.1 soon.  
Since full gateway recovery only happens on a full cluster restart, you  
might have not encountered it. Luckily, since the bug is only on the  
recovery side, a way to solve this is to issue a full cluster shutdown  
(always using the API), replace with latest master (or wait for 0.9.1), and  
then start again the cluster.

-shay.banon

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:20am UTC](https://discuss.elastic.co/t/notice-s3-gateway-critical-bug/3215/2 "2017-07-06T04:20:49Z")

</div>

Closed on July 6, 2017, 4:20am UTC