# Index mgmt as it relates to elastic ingest rate

**URL:** <https://discuss.elastic.co/t/index-mgmt-as-it-relates-to-elastic-ingest-rate/193835>\
**Category:** Elasticsearch\
**Created:** [August 5, 2019, 3:39pm UTC](https://discuss.elastic.co/t/index-mgmt-as-it-relates-to-elastic-ingest-rate/193835 "2019-08-05T15:39:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [August 5, 2019, 3:39pm UTC](https://discuss.elastic.co/t/index-mgmt-as-it-relates-to-elastic-ingest-rate/193835/1 "2019-08-05T15:39:41Z")

</div>

Im running into some problems with elastic ingest.

We're running 5 data nodes on kubernetes (hosts have 56 cores / 64Gb RAM). Data is coming as beats -\> kafka -\> logstash (also via k8) -\> elastic

Ingest rate seems to be topping out at 200-300 e/s so we're lagging considerably behind our data feed.

Seeing errors like this pretty frequently:

```
[logstash.outputs.elasticsearch] retrying failed action with response code: 429 ({"type"=>"es_rejected_execution_exception", "reason"=>"rejected execution of processing of [7142251][indices:data/write/bulk[s][p]]: request: BulkShardRequest [[filebeat-2019.08.05][0]] containing [124] requests, target allocation id: aSctrLvyTpSZkzPqVIvE0A, primary term: 2 on EsThreadPoolExecutor[name = elasticsearch-data-1/write, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@8085181[Running, pool size = 1, active threads = 1, queued tasks = 200, completed tasks = 5601415]]"})

```

Looking at the above index ("filebeat-2019.08.05") it's 30Gb (with \>40M docs) (and growing).

Questions:

1. Should I start rolling this index over every hour?
2. My cluster has ~2600 primary shards and ~800 indexes. Too many?
3. I've split up my busier inputs into separate pipelines. On several of these Im seeing "output" values like "1.92k ms/e". Is this latency due to something I have (mis)configured?

Cluster is all 7.3.0 - 5 data nodes, 5 ingest and 3 master.

---

<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:** [September 2, 2019, 3:39pm UTC](https://discuss.elastic.co/t/index-mgmt-as-it-relates-to-elastic-ingest-rate/193835/2 "2019-09-02T15:39:47Z")

</div>

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