Open heyarny opened 10 years ago
I have now downgraded back to ES 1.0.0, MongoDBRiver 2.0.0 and MongoDB 2.4.10. Removed all indexes (_river and main index). The first configuration with initial import worked just fine. Restarted ES and getting the same error again:
[2014-08-04 16:20:05,954][INFO ][node ] [Stylios Main] version[1.0.0], pid[26352], build[a46900e/2014-02-12T16:18:34Z]
[2014-08-04 16:20:05,955][INFO ][node ] [Stylios Main] initializing ...
[2014-08-04 16:20:05,982][INFO ][plugins ] [Stylios Main] loaded [mongodb-river, mapper-attachments], sites [river-mongodb]
[2014-08-04 16:20:07,595][TRACE][rest.action.mongodb ] [Stylios Main] RestMongoDBRiverAction - baseUrl: /_river/mongodb
[2014-08-04 16:20:07,660][INFO ][node ] [Stylios Main] initialized
[2014-08-04 16:20:07,660][INFO ][node ] [Stylios Main] starting ...
[2014-08-04 16:20:07,731][INFO ][transport ] [Stylios Main] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/144.76.xxx.xxx:9300]}
[2014-08-04 16:20:10,746][INFO ][cluster.service ] [Stylios Main] new_master [Stylios Main][LGdaDMCWQa28GoHAKPdC0w][stylios][inet[/144.76.xxx.xxx:9300]], reason: zen-disco-join (elected_as_master)
[2014-08-04 16:20:10,761][INFO ][discovery ] [Stylios Main] stylios/LGdaDMCWQa28GoHAKPdC0w
[2014-08-04 16:20:10,774][INFO ][http ] [Stylios Main] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/144.76.xxx.xxx:9200]}
[2014-08-04 16:20:11,363][INFO ][gateway ] [Stylios Main] recovered [2] indices into cluster_state
[2014-08-04 16:20:11,521][INFO ][node ] [Stylios Main] started
[2014-08-04 16:20:12,029][TRACE][org.elasticsearch.river.mongodb.MongoDBRiver] Initializing river : [mongodb]
[2014-08-04 16:20:12,031][INFO ][river.mongodb ] Parse river settings for mongodb
[2014-08-04 16:20:12,033][TRACE][river.mongodb ] mongoServersSettings: [{port=27017, host=144.76.xxx.xxx}]
[2014-08-04 16:20:12,034][INFO ][river.mongodb ] Server: 144.76.xxx.xxx - 27017
[2014-08-04 16:20:12,092][INFO ][org.elasticsearch.river.mongodb.MongoDBRiver] Starting river mongodb
[2014-08-04 16:20:12,094][WARN ][org.elasticsearch.river.mongodb.MongoDBRiver] Fail to start river mongodb
org.elasticsearch.action.NoShardAvailableActionException: [_river][3] null
at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.perform(TransportShardSingleOperationAction.java:145)
at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.onFailure(TransportShardSingleOperationAction.java:132)
at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.access$900(TransportShardSingleOperationAction.java:97)
at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[2014-08-04 16:20:12,095][DEBUG][river.mongodb.util ] setRiverStatus called with mongodb - START_FAILED
I know this issue (or similar?) was discussed in history versions, but I couldn't find any solution yet. On ES this issue or similar was marked as fixed, yet I get this using ES 1.2.2, MongoDB 2.6.3 and MongoDBRiver 2.0.1. I have the same config running on another server without any issues. The very first configuration and initial import works just fine, but as soon I restart ES I get this.
Any idea what the cause might be?