# Response Code When No Space

**URL:** <https://discuss.elastic.co/t/response-code-when-no-space/59625>\
**Category:** Elasticsearch\
**Created:** [September 2, 2016, 6:20am UTC](https://discuss.elastic.co/t/response-code-when-no-space/59625 "2016-09-02T06:20:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![geek876](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geek876/32/9329_2.png) [@geek876](https://discuss.elastic.co/u/geek876)\
**Post date:** [September 2, 2016, 6:20am UTC](https://discuss.elastic.co/t/response-code-when-no-space/59625/1 "2016-09-02T06:20:30Z")

</div>

Hi,  
We use ElasticSearch to store events from fluentd. Recently our elasticsearch cluster was 100% full but even then there were no errors at fluentd level and it continued to push events to ES although the data seems to have gone to a black hole.

To investigate this, I would like to know what response code ES would give back to fluent(or any client via HTTP API) when storing data when:

1. Storage was successful.
2. Storage was not-successful due to no more free space left.
3. Storage was not-successful due to some other reason.

Thanks.

---

<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 5, 2017, 10:22pm UTC](https://discuss.elastic.co/t/response-code-when-no-space/59625/2 "2017-07-05T22:22:57Z")

</div>

Closed on July 5, 2017, 10:22pm UTC