# Mysql to Logstash data migration!

**URL:** <https://discuss.elastic.co/t/mysql-to-logstash-data-migration/108534>\
**Category:** Elasticsearch\
**Created:** [November 21, 2017, 9:10am UTC](https://discuss.elastic.co/t/mysql-to-logstash-data-migration/108534 "2017-11-21T09:10:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gobinda\_Nandi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gobinda_nandi/32/24506_2.png) [@Gobinda\_Nandi](https://discuss.elastic.co/u/Gobinda_Nandi)\
**Post date:** [November 21, 2017, 9:10am UTC](https://discuss.elastic.co/t/mysql-to-logstash-data-migration/108534/1 "2017-11-21T09:10:28Z")

</div>

I have a **logstash.conf** file running and scheduled every after one minute. Will this make my site **slower** and get **crashed**?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 21, 2017, 12:29pm UTC](https://discuss.elastic.co/t/mysql-to-logstash-data-migration/108534/2 "2017-11-21T12:29:33Z")

</div>

Dumping a database every minute puts some pressure for sure on the database.

I shared thoughts about this strategy here: [http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/](http://david.pilato.fr/blog/2015/05/09/advanced-search-for-your-legacy-application/)

---

<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 19, 2017, 12:29pm UTC](https://discuss.elastic.co/t/mysql-to-logstash-data-migration/108534/3 "2017-12-19T12:29:50Z")

</div>

Closed on December 19, 2017, 12:29pm UTC

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