# Metric beat unable to write data

**URL:** <https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [September 1, 2018, 12:24am UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926 "2018-09-01T00:24:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ReasonDuan](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@ReasonDuan](https://discuss.elastic.co/u/ReasonDuan)\
**Post date:** [September 1, 2018, 12:24am UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926/1 "2018-09-01T00:24:53Z")

</div>

When crossing the day, when the data needs to be written to the new index, the ES will be unable to write.  
Then I stop some metricbeat instances and it will return to normal.

- Metricbeat Version: 6.3.1
- ES Version: 5.5.1
- Operating System: Docker

metricbeat log：  
2018-08-31T00:01:48.598ZRRORlasticsearch/client.go:299ailed to perform any bulk index operations: Post [http://10.16.232.75:8200/\_bulk:](http://10.16.232.75:8200/_bulk:) net/http: request canceled (Client.Timeout exceeded while awaiting headers)  
2018-08-31T00:01:49.598ZRRORipeline/output.go:92ailed to publish events: Post [http://10.16.232.75:8200/\_bulk:](http://10.16.232.75:8200/_bulk:) net/http: request canceled (Client.Timeout exceeded while awaiting headers)  
2018-08-31T00:01:50.688ZRRORipeline/output.go:92ailed to publish events: temporary bulk send failure  
2018-08-31T00:01:51.774ZRRORipeline/output.go:92ailed to publish events: temporary bulk send failure

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 1, 2018, 3:24pm UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926/2 "2018-09-01T15:24:08Z")

</div>

Is there anything in the Elasticsearch logs? What is the output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-stats.html)? Is there something causing cluster updates to be slow, e.g. large mappings or very large number of indices/shards?

---

<div class="post-metadata">

**Author:** ![ReasonDuan](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@ReasonDuan](https://discuss.elastic.co/u/ReasonDuan)\
**Post date:** [September 7, 2018, 12:15am UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926/3 "2018-09-07T00:15:01Z")

</div>

Thank you. The reason is in than our Elasticsearch cluster is creating new index at the time, but the cluster create new index is very slow (about 40 second).When we create the index in advance, everything will be normal.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 7, 2018, 5:14am UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926/4 "2018-09-07T05:14:55Z")

</div>

How many indices are typically created at a time?

---

<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:** [October 5, 2018, 5:14am UTC](https://discuss.elastic.co/t/metric-beat-unable-to-write-data/146926/5 "2018-10-05T05:14:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
