# Logstash Output to Elasticsearch - Try Once Logic

**URL:** https://discuss.elastic.co/t/logstash-output-to-elasticsearch-try-once-logic/231403
**Category:** Logstash
**Created:** [May 6, 2020, 8:14pm UTC](https://discuss.elastic.co/t/logstash-output-to-elasticsearch-try-once-logic/231403 "2020-05-06T20:14:34Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![seth.yes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seth.yes/32/11788_2.png) [@seth.yes](https://discuss.elastic.co/u/seth.yes)
#### Post date: [May 6, 2020, 8:14pm UTC](https://discuss.elastic.co/t/logstash-output-to-elasticsearch-try-once-logic/231403/1 "2020-05-06T20:14:34Z")

</div>

I have a cluster that processes around 200k netflow records every second. Due to this volume of throughput, the ES cluster intermittently gets behind on indexing, returning a 503. This increases the pipeline latency, as Logstash keeps trying to send the same data and more data just backs up behind it, thus exacerbating the issue. Furthermore, I have a kafka output plugin that never gets this data while ES is trying to catch up.

Is there a way to get Logstash to just try once to index a document and then just move on? I've tried the following settings to no avail:

```auto
output {
  elasticsearch {
    id => "my_unique_id"
    hosts => [<my ES nodes>]
    retry_initial_interval => 0
    retry_max_interval => 0
    retry_on_conflict => 0
    index => "busy_index"
  }
}

```

---

<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: [June 3, 2020, 8:14pm UTC](https://discuss.elastic.co/t/logstash-output-to-elasticsearch-try-once-logic/231403/2 "2020-06-03T20:14:36Z")

</div>

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