# Upgrade Logstash Elasticsearch output plugin without updating Logstash core

**URL:** <https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535>\
**Category:** Logstash\
**Created:** [August 1, 2018, 10:15am UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535 "2018-08-01T10:15:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Denis\_Filatov](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@Denis\_Filatov](https://discuss.elastic.co/u/Denis_Filatov)\
**Post date:** [August 1, 2018, 10:15am UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/1 "2018-08-01T10:15:47Z")

</div>

Hello!

We using 5.1.2 version of Elastic stack (Logstash, Kibana, Elastic).  
And now we need to dead letter queue feature.

The best way i see - upgrade only elasticsearch output plugin from Version: 5.4.0 to version Version 7.4.2.  
I don't see any restrictions to do that in Docs, but upgrade on two major versions often leds to changing in core APIs or any changes without backward compatibility.

Maybe proposed way to update is OK or another way is possible?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 1, 2018, 11:59am UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/2 "2018-08-01T11:59:25Z")

</div>

Wasn't the dead letter queue feature added after Logstash 5.1? If so it won't matter if you'll be able to upgrade the plugin.

But more generally, if a plugin upgrade succeeds things _should_ be fine.

---

<div class="post-metadata">

**Author:** ![Denis\_Filatov](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@Denis\_Filatov](https://discuss.elastic.co/u/Denis_Filatov)\
**Post date:** [August 1, 2018, 12:12pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/3 "2018-08-01T12:12:38Z")

</div>

The first mention of DLQ feature i have been see in 5.5 version of Elastic Stack:  
[https://www.elastic.co/guide/en/logstash/5.5/dead-letter-queues.html](https://www.elastic.co/guide/en/logstash/5.5/dead-letter-queues.html)

Am i right that i can only install the new version of Elastic output plugin from 5.6 version of ELK to my Logsatsh from 5.1 version of ELK ant it fill be work?

Sorry for double check questions, because i accustomed that we should always upgrade all stack instead of upgrade some parts or plugins.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 1, 2018, 12:34pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/4 "2018-08-01T12:34:28Z")

</div>

> Am i right that i can only install the new version of Elastic output plugin from 5.6 version of ELK to my Logsatsh from 5.1 version of ELK ant it fill be work?

If the dead letter queue feature was introduced in Logstash 5.6 then you need Logstash 5.6.

---

<div class="post-metadata">

**Author:** ![Denis\_Filatov](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@Denis\_Filatov](https://discuss.elastic.co/u/Denis_Filatov)\
**Post date:** [August 1, 2018, 1:26pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/5 "2018-08-01T13:26:03Z")

</div>

> [@magnusbaeck](#):
>
> If the dead letter queue feature was introduced in Logstash 5.6 than you need Logstash 5.6.

OK, understood. Thank you!

And update of Logsatsh from 5.1.2 to 5.6 automatically leads to update Elasticsearch and Kibana.  
It's hard for us, but we will think about that.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 1, 2018, 2:03pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/6 "2018-08-01T14:03:20Z")

</div>

> And update of Logsatsh from 5.1.2 to 5.6 automatically leads to update Elasticsearch and Kibana.  
> It's hard for us, but we will think about that.

Given the very weak dependencies between Logstash and ES I think such a policy is completely unnecessary and overly risk-aversive.

---

<div class="post-metadata">

**Author:** ![Denis\_Filatov](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@Denis\_Filatov](https://discuss.elastic.co/u/Denis_Filatov)\
**Post date:** [August 1, 2018, 2:16pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/7 "2018-08-01T14:16:49Z")

</div>

Big thanks for your comments!

---

<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:** [August 29, 2018, 2:16pm UTC](https://discuss.elastic.co/t/upgrade-logstash-elasticsearch-output-plugin-without-updating-logstash-core/142535/8 "2018-08-29T14:16:56Z")

</div>

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