# Logstash JDBC plugin and high availability

**URL:** <https://discuss.elastic.co/t/logstash-jdbc-plugin-and-high-availability/156322>\
**Category:** Logstash\
**Created:** [November 12, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-jdbc-plugin-and-high-availability/156322 "2018-11-12T16:24:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anp](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@anp](https://discuss.elastic.co/u/anp)\
**Post date:** [November 12, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-jdbc-plugin-and-high-availability/156322/1 "2018-11-12T16:24:10Z")

</div>

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:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 10, 2018, 4:24pm UTC](https://discuss.elastic.co/t/logstash-jdbc-plugin-and-high-availability/156322/2 "2018-12-10T16:24:21Z")

</div>

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