search

jprante / elasticsearch-jdbc

JDBC importer for Elasticsearch
Apache License 2.0
2.84k stars 710 forks source link

client closed error #407

Open vijaydodla opened 9 years ago

vijaydodla commented 9 years ago

Hi We are using river JDBC in our platform and we are seeing below issues in one environment . In Dev servers we are not seeing these issues. Can you please throw some light on this . we are using river for a schedule job which fires every mnt .

[ERROR][Feeder ] error while getting next input: client is closed org.elasticsearch.ElasticsearchIllegalStateException: client is closed at org.xbib.elasticsearch.support.client.node.NodeClient.newIndex(NodeClient.java:318) at org.xbib.elasticsearch.support.client.node.NodeClient.newIndex(NodeClient.java:38) at org.xbib.elasticsearch.plugin.feeder.jdbc.JDBCFeeder.startBulk(JDBCFeeder.java:286) at org.xbib.elasticsearch.plugin.feeder.jdbc.JDBCFeeder.executeTask(JDBCFeeder.java:138) at org.xbib.elasticsearch.plugin.feeder.AbstractFeeder.newRequest(AbstractFeeder.java:361) at org.xbib.elasticsearch.plugin.feeder.AbstractFeeder.newRequest(AbstractFeeder.java:52) at org.xbib.pipeline.AbstractPipeline.call(AbstractPipeline.java:86) at org.xbib.pipeline.AbstractPipeline.call(AbstractPipeline.java:17) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [2014-12-09 22:21:37,010][INFO ][Feeder ] close (no-op) [2014-12-09 22:21:37,010][INFO ][JDBCFeeder ] reading connection closed [2014-12-09 22:21:37,010][INFO ][JDBCFeeder ] writing connection closed

sawickil commented 9 years ago

not sure if this is helpful but we was getting such a kind of problems when queries were taking more than the interval defined in the scheduler and the thread-pool was set to >1. See https://github.com/jprante/elasticsearch-river-jdbc/issues/398. However, I don't know the root cause.