# Index : MySQL to Elasticsearch 6.2 with Logstash 6.2 **URL:** https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573 **Category:** Elasticsearch **Created:** [May 12, 2018, 2:04pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573 "2018-05-12T14:04:54Z") **Posts on this page:** 20 **Page:** 1
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 12, 2018, 2:04pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/1 "2018-05-12T14:04:54Z")
Hi, I'm trying to use Logstash 6.2 and mysql-connector-java-8.0.11 to import rows from MySQL server to ElasticSearch 6.2. Everything seems working unless the creation of the index in Elasticsearch. I thought it was automatically created but apparently it isn't. How to create an index according to the mysql configuration (even if this is absolutely not the same architecture) ? Here my Logstash conf : input { jdbc { jdbc\_connection\_string =\> "jdbc:mysql://address:3306/db" jdbc\_user =\> "user" jdbc\_password =\> "pass" jdbc\_validate\_connection =\> true jdbc\_driver\_library =\> "./../mysql-connector-java-8.0.11/mysql-connector-java-8.0.11-bin.jar" jdbc\_driver\_class =\> "com.mysql.jdbc.Driver" jdbc\_fetch\_size =\> 100 schedule =\> "\* \* \* \* \*" statement =\> "SELECT \* FROM table" } } output { elasticsearch { index =\> "indexer" document\_type =\> "typer" document\_id =\> "%{id}" hosts =\> ["localhost:9200"] user =\> "user" password =\> "pass" template\_overwrite =\> true template =\> "/etc/logstash/defaultemplate.json" } } And the template can be found here : [https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template-es6x.json](https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template-es6x.json) Thanks for reading me and the help you could offer 🙂 ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 12, 2018, 11:22pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/2 "2018-05-12T23:22:01Z")
Elasticsearch, by default, will automatically create the index on first document being indexed. Why do you think that the index `indexer` was not created? ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 13, 2018, 8:58am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/3 "2018-05-13T08:58:58Z")
Thank you for your reply. 🙂 When I enter > curl localhost:9200/\_cat/indices I didn't see the index listed. So I created it manually. But it never fills. I use x-pack, if it changes something. ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 13, 2018, 3:27pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/4 "2018-05-13T15:27:12Z")
The index should have been created automatically when the first document gets indexed. That being said, if you created it manually and still doesn't fills I suspect that you are with indexing errors in Logstash. Please, attach Logstash logs, also attach the content of "/etc/logstash/defaultemplate.json" ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 13, 2018, 5:46pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/5 "2018-05-13T17:46:57Z")
Here, my logs for Logstash > [2018-05-13T19:24:06,168][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.2.4"} > [2018-05-13T19:24:06,279][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600} > [2018-05-13T19:24:06,667][WARN][logstash.outputs.elasticsearch] You are using a deprecated config setting "document\_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=\>"document\_type", :plugin=\>\[[http://127.0.0.1:9200](http://127.0.0.1:9200)], bulk\_path=\>"/\_xpack/monitoring/\_bulk?system\_id=logstash&system\_api\_version=2&interval=1s", manage\_template=\>false, document\_type=\>"%{[@metadata][document\_type]}", sniffing=\>false, user=\>"user", password=\>, id=\>"5945ca2417ad319868d778c7400d214bb01ea322355cce4f402badcb5090c9df", enable\_metric=\>true, codec=\>\"plain\_c816780e-8635-47c6-8ad3-553370d2452c", enable\_metric=\>true, charset=\>"UTF-8"\>, workers=\>1, template\_name=\>"logstash", template\_overwrite=\>false, doc\_as\_upsert=\>false, script\_type=\>"inline", script\_lang=\>"painless", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_initial\_interval=\>2, retry\_max\_interval=\>64, retry\_on\_conflict=\>1, action=\>"index", ssl\_certificate\_verification=\>true, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false\>} > [2018-05-13T19:24:06,675][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>".monitoring-logstash", "pipeline.workers"=\>1, "pipeline.batch.size"=\>2, "pipeline.batch.delay"=\>50} > [2018-05-13T19:24:06,922][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)]}} > [2018-05-13T19:24:06,926][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/), :path=\>"/"} > [2018-05-13T19:24:07,107][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)"} > [2018-05-13T19:24:07,146][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es\_version=\>6} > [2018-05-13T19:24:07,146][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} > [2018-05-13T19:24:07,148][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::Elasticsearch", :hosts=\>["[http://127.0.0.1:9200](http://127.0.0.1:9200)"]} > [2018-05-13T19:24:07,209][INFO][logstash.licensechecker.licensereader] Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)]}} > [2018-05-13T19:24:07,209][INFO][logstash.licensechecker.licensereader] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/), :path=\>"/"} > [2018-05-13T19:24:07,213][WARN][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=\>"[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)"} > [2018-05-13T19:24:07,218][INFO][logstash.licensechecker.licensereader] ES Output version determined {:es\_version=\>6} > [2018-05-13T19:24:07,219][WARN][logstash.licensechecker.licensereader] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} > [2018-05-13T19:24:07,248][INFO][logstash.pipeline] Pipeline started successfully {:pipeline\_id=\>".monitoring-logstash", :thread=\>"#\"} > [2018-05-13T19:24:07,966][WARN][logstash.outputs.elasticsearch] You are using a deprecated config setting "document\_type" set in elasticsearch. Deprecated settings will continue to work, but are scheduled for removal from logstash in the future. Document types are being deprecated in Elasticsearch 6.0, and removed entirely in 7.0. You should avoid this feature If you have any questions about this, please visit the #logstash channel on freenode irc. {:name=\>"document\_type", :plugin=\>\[[//localhost:9200](https://localhost:9200)], user=\>"user", password=\>, sniffing=\>true, manage\_template=\>false, index=\>"%{[@metadata][beat]}-%{+YYYY.MM.dd}", document\_type=\>"%{[@metadata][type]}", id=\>"86c7d5c366bfbb8a3698157dcf310bc815f5323314055bddc92f3e80ddcc5300", enable\_metric=\>true, codec=\>\"plain\_d8128abc-fdc3-440a-97e6-b77b785841bf", enable\_metric=\>true, charset=\>"UTF-8"\>, workers=\>1, template\_name=\>"logstash", template\_overwrite=\>false, doc\_as\_upsert=\>false, script\_type=\>"inline", script\_lang=\>"painless", script\_var\_name=\>"event", scripted\_upsert=\>false, retry\_initial\_interval=\>2, retry\_max\_interval=\>64, retry\_on\_conflict=\>1, action=\>"index", ssl\_certificate\_verification=\>true, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false\>} > [2018-05-13T19:24:08,006][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>"main", "pipeline.workers"=\>8, "pipeline.batch.size"=\>125, "pipeline.batch.delay"=\>50} > [2018-05-13T19:24:08,018][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/)]}} > [2018-05-13T19:24:08,020][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/), :path=\>"/"} > [2018-05-13T19:24:08,029][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/)"} > [2018-05-13T19:24:08,037][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es\_version=\>6} > [2018-05-13T19:24:08,037][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 13, 2018, 5:51pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/6 "2018-05-13T17:51:04Z")
Due the fact that I can't post more than 7000 characters, I split my logs 😉 > [2018-05-13T19:24:08,039][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::Elasticsearch", :hosts=\>["[//localhost:9200](https://localhost:9200)"]} > [2018-05-13T19:24:08,046][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/)]}} > [2018-05-13T19:24:08,047][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/), :path=\>"/"} > [2018-05-13T19:24:08,053][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/)"} > [2018-05-13T19:24:08,059][INFO][logstash.outputs.elasticsearch] ES Output version determined {:es\_version=\>6} > [2018-05-13T19:24:08,060][WARN][logstash.outputs.elasticsearch] Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>6} > [2018-05-13T19:24:08,060][INFO][logstash.outputs.elasticsearch] Using mapping template from {:path=\>nil} > [2018-05-13T19:24:08,064][INFO][logstash.outputs.elasticsearch] Attempting to install template {:manage\_template=\>{"template"=\>"logstash-_", "version"=\>60001, "settings"=\>{"index.refresh\_interval"=\>"5s"}, "mappings"=\>{"default"=\>{"dynamic\_templates"=\>[{"message\_field"=\>{"path\_match"=\>"message", "match\_mapping\_type"=\>"string", "mapping"=\>{"type"=\>"text", "norms"=\>false}}}, {"string\_fields"=\>{"match"=\>"_", "match\_mapping\_type"=\>"string", "mapping"=\>{"type"=\>"text", "norms"=\>false, "fields"=\>{"keyword"=\>{"type"=\>"keyword", "ignore\_above"=\>256}}}}}], "properties"=\>{"@timestamp"=\>{"type"=\>"date"}, "@version"=\>{"type"=\>"keyword"}, "geoip"=\>{"dynamic"=\>true, "properties"=\>{"ip"=\>{"type"=\>"ip"}, "location"=\>{"type"=\>"geo\_point"}, "latitude"=\>{"type"=\>"half\_float"}, "longitude"=\>{"type"=\>"half\_float"}}}}}}}} > [2018-05-13T19:24:08,072][INFO][logstash.outputs.elasticsearch] New Elasticsearch output {:class=\>"LogStash::Outputs::Elasticsearch", :hosts=\>["[//localhost:9200](https://localhost:9200)"]} > [2018-05-13T19:24:08,484][INFO][logstash.inputs.beats] Beats inputs: Starting input listener {:address=\>"0.0.0.0:5044"} > [2018-05-13T19:24:08,675][INFO][logstash.pipeline] Pipeline started successfully {:pipeline\_id=\>"main", :thread=\>"#\"} > [2018-05-13T19:24:08,678][INFO][org.logstash.beats.Server] Starting server on port: 5044 > [2018-05-13T19:24:08,688][INFO][logstash.agent] Pipelines running {:count=\>2, :pipelines=\>[".monitoring-logstash", "main"]} > [2018-05-13T19:24:08,689][INFO][logstash.inputs.metrics] Monitoring License OK > [2018-05-13T19:24:13,051][INFO][logstash.outputs.elasticsearch] Elasticsearch pool URLs updated {:changes=\>{:removed=\>[[http://user:pass@localhost:9200/](http://user:pass@localhost:9200/)], :added=\>[[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)]}} > [2018-05-13T19:24:13,053][INFO][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck\_url=\>[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/), :path=\>"/"} > [2018-05-13T19:24:13,057][WARN][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=\>"[http://user:pass@127.0.0.1:9200/](http://user:pass@127.0.0.1:9200/)"} And here, you can find the /etc/logstash/defaultemplate.json that I found [there](https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template-es6x.json) : ``` { "template" : "places", "version" : 60001, "settings" : { "index.refresh_interval" : "5s" }, "mappings" : { "_default_" : { "dynamic_templates" : [ { "message_field" : { "path_match" : "message", "match_mapping_type" : "string", "mapping" : { "type" : "text", "norms" : false } } }, { "string_fields" : { "match" : "*", "match_mapping_type" : "string", "mapping" : { "type" : "text", "norms" : false, "fields" : { "keyword" : { "type": "keyword", "ignore_above": 256 } } } } } ], "properties" : { "@timestamp": { "type": "date"}, "@version": { "type": "keyword"}, "geoip" : { "dynamic": true, "properties" : { "ip": { "type": "ip" }, "location" : { "type" : "geo_point" }, "latitude" : { "type" : "half_float" }, "longitude" : { "type" : "half_float" } } } } } } } ``` But even without this template, the index never fills. Thank you for your time 🙂 ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 13, 2018, 6:23pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/7 "2018-05-13T18:23:04Z")
Your log is presenting this: ```auto [2018-05-13T19:24:08,484][INFO][logstash.inputs.beats] Beats inputs: Starting input listener {:address=>"0.0.0.0:5044"} ``` Which means that it is starting a Beats input while your configuration is just using JDBC. Also, the logs does not shows the JDBC starting up. So I would say that the configuration you presented here is not the one being used by Logstash. Additionally, this is not directly related, but it is worth mentioning that this index template will not be used for the `indexer` index since it's `template` attribute is set to `places`. If you wish to use that template for `indexer` index then you need to set `"template": "indexer"`. ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 13, 2018, 9:05pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/8 "2018-05-13T21:05:09Z")
This is because I changed the name of the index. I also have some others config files which work. My problem only comes with JCDB's config file. ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 13, 2018, 11:31pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/9 "2018-05-13T23:31:13Z")
Ok, so run Logstash with `--log.level debug`, let it run for a few seconds (to produce more logs), upload the content to a [gist](https://gist.github.com/) (or maybe [pastebin](https://pastebin.com/)) and post the link here ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 9:47am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/10 "2018-05-14T09:47:53Z")
I usually launch Logstash as service. But I tried this command > sudo /usr/share/logstash/bin/logstash -f --log.level=debug --path.settings /etc/logstash/conf.d/places.conf Which gave me this error > ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/etc/logstash/conf.d/places.conf, exception=Java::JavaLang::RuntimeException, message=\>Unhandled IOException: java.io.IOException: unhandled errno: Not a directory > [ERROR] 2018-05-14 11:41:59.673 [main] Logstash - java.lang.IllegalStateException: org.jruby.exceptions.RaiseException: (SystemExit) exit So my conclusion is JCDB is not allowed to read content of conf.d, is that true ? ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 14, 2018, 10:26am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/11 "2018-05-14T10:26:03Z")
You can still start it as a service and you may set `log.level` in `/etc/logstash/logstash.yml` ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 10:47am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/12 "2018-05-14T10:47:06Z")
I added log.level in logstash.yml and I restarted logstash via service. [Here](https://gist.github.com/phenric/510fa6efd31cdd3ba36e85ca340f0234), you can find every logs since the restart. Again, thank you ! 🙂 ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 14, 2018, 11:02am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/13 "2018-05-14T11:02:47Z")
When you execute the SQL Query `SELECT id, extID, name, address, postcode, country, city FROM Place` does it returns any result at all? ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 11:34am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/14 "2018-05-14T11:34:41Z")
> [@thiago](#): > > SELECT id, extID, name, address, postcode, country, city FROM Place Yes, it does ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 14, 2018, 11:36am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/15 "2018-05-14T11:36:03Z")
Ok, so we need tracing here. Set it to `log.level: trace` and re-execute. ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 11:52am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/16 "2018-05-14T11:52:28Z")
[Here](https://gist.github.com/phenric/7113143ee4238581047190267c35ae0b), the logs with trace 🙂 ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 14, 2018, 11:55am UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/17 "2018-05-14T11:55:20Z")
Can you please let it run for a few minutes? Also, when you execute the query in MySQL directory (through another client), how long does it takes until it _finishes_? ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 12:19pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/18 "2018-05-14T12:19:11Z")
Sure ! [Here](https://gist.github.com/phenric/7e165d105957bc7d9543188dae42a0ad) during 12 minutes. When I execute the query in another client it's immediate. ---
### Author: ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago) #### Post date: [May 14, 2018, 12:37pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/19 "2018-05-14T12:37:26Z")
I don't see any issues in the logs so either the database table is empty or rows got into Elasticsearch. What's the output of: ```auto curl localhost:9200/_cat/indices?v ``` ---
### Author: ![phenric](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@phenric](https://discuss.elastic.co/u/phenric) #### Post date: [May 14, 2018, 1:00pm UTC](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573/20 "2018-05-14T13:00:59Z")
Only indices with a point in the front (i.e. .monitoring-logstash-6-2018.05.10) all in green and an index 'cat' in yellow. No other index. But is it possible that is due by something else like JAVA or JCDB ? Because of there is this issue: > [2018-05-14T12:36:04,792][DEBUG][io.netty.util.internal.NativeLibraryLoader] Unable to load the library 'netty\_tcnative\_linux\_x86\_64', trying other loading mechanism. > java.lang.UnsatisfiedLinkError: no netty\_tcnative\_linux\_x86\_64 in java.library.path [Next page](https://discuss.elastic.co/t/index-mysql-to-elasticsearch-6-2-with-logstash-6-2/131573.md?page=2)