# Disabling retries for Elasticsearch output plugin

**URL:** <https://discuss.elastic.co/t/disabling-retries-for-elasticsearch-output-plugin/212798>\
**Category:** Logstash\
**Created:** [December 23, 2019, 2:16am UTC](https://discuss.elastic.co/t/disabling-retries-for-elasticsearch-output-plugin/212798 "2019-12-23T02:16:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tonyc](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@tonyc](https://discuss.elastic.co/u/tonyc)\
**Post date:** [December 23, 2019, 2:16am UTC](https://discuss.elastic.co/t/disabling-retries-for-elasticsearch-output-plugin/212798/1 "2019-12-23T02:16:13Z")

</div>

Hi all,

Does anyone know if it's possible to configure an Elasticsearch Logstash output to completely ignore failures?

I'm setting up a new Elasticsearch cluster and I want my existing Logstash pipeline to output to both our current production cluster + the new cluster.

However, for the new cluster, I don't want Logstash to keep logs in memory in the event of an error from the new cluster.

Is this possible? I looked through the configuration options for the Elasticsearch output and it doesn't seem to be the case, but I thought I would double check here.

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:** [January 20, 2020, 2:16am UTC](https://discuss.elastic.co/t/disabling-retries-for-elasticsearch-output-plugin/212798/2 "2020-01-20T02:16:17Z")

</div>

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