2

I am using the elasticsearch jdbc river plugin, and I have a simple SQL table with 11 million rows. But when I use it to index the table, it stops somewhere at 2 million rows. On checking the elasticsearch log file, I did not find any errors. Does anyone know why that is happening?

dickyj
  • 1,830
  • 1
  • 24
  • 41
  • +1, I have the same exact issue – user2694306 Jun 10 '14 at 09:54
  • 1
    After I upgraded to version 1.2 of elasticsearch and version 1.2.1 of the elasticsearch river jdbc plugin, the problem went away, I was able to index all of the rows. – dickyj Jun 10 '14 at 10:04
  • 1
    I think that we all had the same issue with the river. I have posted a similar question a month ago and still didn't get an answer. The problem is related to the queue capacity. I think that the best thing to do is to open a issue about it in the plugin repo – eliasah Jun 11 '14 at 19:51

0 Answers0