# High availability of logstash using jdbc plugin

**URL:** https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043
**Category:** Logstash
**Created:** [January 22, 2020, 11:03am UTC](https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043 "2020-01-22T11:03:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![naveenbangalore](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@naveenbangalore](https://discuss.elastic.co/u/naveenbangalore)
#### Post date: [January 22, 2020, 11:03am UTC](https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043/1 "2020-01-22T11:03:50Z")

</div>

I have a 2 node logstash setup populating the elastic cluster. There are few configs that use the jdbc plugin in the input. Is there a way to setup high availability among the logstash nodes when one of them fails? My query is the same as the one in the below link, however, I am raising it again since there were no responses to that.

> [@Logstash JDBC plugin and high availability](https://discuss.elastic.co/t/logstash-jdbc-plugin-and-high-availability/156322):
>
> I have an Elasticsearch cluster populated via the Logstash JDBC plugin, Is there a way to make Logstash highly available? Ideally I want only one instance of Logstash polling the relational database at a time and have this instance failover if it crashes.

---

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [January 22, 2020, 2:44pm UTC](https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043/2 "2020-01-22T14:44:17Z")

</div>

No, logstash does not support clustering where one of a group of nodes performs an operation.

---

<div class="post-metadata">

### Author: ![siriusblock](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/siriusblock/32/45680_2.png) [@siriusblock](https://discuss.elastic.co/u/siriusblock)
#### Post date: [February 10, 2020, 2:52pm UTC](https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043/3 "2020-02-10T14:52:01Z")

</div>

It seems only option is to generate id's using fingerprint plugin and in elasticsearch output use document\_id =\> "%{[@metadata][fingerprint]}". But you have to accept the fact, that you make more queries to your db and cost of updating elasticsearch index and using generated id's.

---

<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: [March 9, 2020, 2:52pm UTC](https://discuss.elastic.co/t/high-availability-of-logstash-using-jdbc-plugin/216043/4 "2020-03-09T14:52:13Z")

</div>

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