# Solutions for syncing MySQL with Elasticsearch

**URL:** <https://discuss.elastic.co/t/solutions-for-syncing-mysql-with-elasticsearch/81207>\
**Category:** Elasticsearch\
**Created:** [April 4, 2017, 7:15pm UTC](https://discuss.elastic.co/t/solutions-for-syncing-mysql-with-elasticsearch/81207 "2017-04-04T19:15:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![avelis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/avelis/32/14689_2.png) [@avelis](https://discuss.elastic.co/u/avelis)\
**Post date:** [April 4, 2017, 7:15pm UTC](https://discuss.elastic.co/t/solutions-for-syncing-mysql-with-elasticsearch/81207/1 "2017-04-04T19:15:56Z")

</div>

Asking the wisdom of the crowds here. Are there a tools available to keep data within a MySQL database in sync with Elasticsearch.

I am currently using an asynchronous queue and batching system within Python but feel it's missing features to be a complete solution.

Namely:

1. Being platform agnostic
2. Some form of polling to determine sync lag has occurred.
3. A way to ensure the queue will finish processing in the event the Elasticsearch is unavailable temporarily for X seconds.

This conversation was spawned when I [observed a non seamless failover with Elastic Cloud](https://discuss.elastic.co/t/received-502-proxy-initializing-and-404-unknown-cluster/81049) and found it worthy to start considering changing my syncing solution that can account for that.

---

<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:** [May 2, 2017, 7:16pm UTC](https://discuss.elastic.co/t/solutions-for-syncing-mysql-with-elasticsearch/81207/2 "2017-05-02T19:16:28Z")

</div>

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