# Error sending data to elasticsearch

**URL:** <https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789>\
**Category:** Elasticsearch\
**Created:** [June 3, 2016, 10:50am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789 "2016-06-03T10:50:50Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 3, 2016, 10:50am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/1 "2016-06-03T10:50:50Z")

</div>

I have come accorss with the following error. Is there anyone who have ideas with that?

> 2016/06/03 10:49:02.295137 client.go:190: INFO Bulk item insert failed (i=49, status=503): {"type":"unavailable\_shards\_exception","reason":"[topbeat-2016.06.03][2] primary shard is not active Timeout: [1m], request: [BulkShardRequest to [topbeat-2016.06.03] containing [10] requests]"}

---

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [June 3, 2016, 10:56am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/2 "2016-06-03T10:56:45Z")

</div>

A 503 can indicate an overload which means the thread pools are busy and so the request is rejected.

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 3, 2016, 11:24am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/3 "2016-06-03T11:24:25Z")

</div>

Yes I found it is the disk size problem  
What files, like old data, and where should I delete in elasticsearch to make the beats feed data again?  
And how can I make the data to just keep for some time and delete automatucally after a certain period as they become old data

---

<div class="post-metadata">

**Author:** ![Nicolas\_Guyomar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_guyomar/32/10124_2.png) [@Nicolas\_Guyomar](https://discuss.elastic.co/u/Nicolas_Guyomar)\
**Post date:** [June 3, 2016, 11:34am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/4 "2016-06-03T11:34:02Z")

</div>

Hi,

You can use curator [https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html) to schedule delete

There are some example [https://www.elastic.co/guide/en/elasticsearch/client/curator/current/examples.html](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/examples.html)

You might want to delete index older than 'x' days for instance

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 6, 2016, 4:19am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/5 "2016-06-06T04:19:46Z")

</div>

When I tried to run the command, it comes across with the following issues.

[Administrator@localhost elasticsearch]$ curator --host 172.16.1.245 delete indices --older-than 2 --time-unit days --timestring '%Y.%m.%d'  
Traceback (most recent call last):  
File "/usr/bin/curator", line 5, in   
from pkg\_resources import load\_entry\_point  
ImportError: No module named pkg\_resources

---

<div class="post-metadata">

**Author:** ![Kennedy\_Kan1](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)\
**Post date:** [June 6, 2016, 4:32am UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/6 "2016-06-06T04:32:21Z")

</div>

I am now coming across with the problem like that

> Exception in thread "main" java.nio.file.FileSystemException: /tmp/2427469249444301473.tmp: No space left on device  
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)  
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  
> at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  
> at java.nio.file.Files.newByteChannel(Files.java:361)  
> at java.nio.file.Files.createFile(Files.java:632)  
> at java.nio.file.TempFileHelper.create(TempFileHelper.java:138)  
> at java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:161)  
> at java.nio.file.Files.createTempFile(Files.java:897)  
> at org.elasticsearch.bootstrap.Security.selfTest(Security.java:352)  
> at org.elasticsearch.bootstrap.Security.configure(Security.java:124)  
> at org.elasticsearch.bootstrap.Bootstrap.setupSecurity(Bootstrap.java:196)  
> at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:167)  
> at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:270)  
> at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)  
> Refer to the log for complete error details.

---

<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:46pm UTC](https://discuss.elastic.co/t/error-sending-data-to-elasticsearch/51789/7 "2017-07-05T22:46:04Z")

</div>

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


