richardwilly98 / elasticsearch-river-mongodb

MongoDB River Plugin for ElasticSearch
1.12k stars 215 forks source link

Cannot start river xxx. Current status is START_FAILED #541

Open johnxjcheng opened 9 years ago

johnxjcheng commented 9 years ago

Hi there,

After install the MongoDB River Plugin (version 2.0.9). I have got a couple of issues to start it. At the beginning it was the authentication issue. I could resolve it by reading the log. However the last one won't show me any detail. Is there a way to get any useful clue?

Here is the log:

[2015-06-24 11:13:49,530][WARN ][bootstrap ] jvm uses the client vm, make sure to run java with the server vm for best performance by adding -server to the command line [2015-06-24 11:13:49,730][INFO ][node ] [node01] version[1.6.0], pid[5256], build[cdd3ac4/2015-06-09T13:36:34Z] [2015-06-24 11:13:49,730][INFO ][node ] [node01] initializing ... [2015-06-24 11:13:49,807][INFO ][plugins ] [node01] loaded [marvel, mapper-attachments, mongodb-river], sites [marvel, head, river-mongodb] [2015-06-24 11:13:50,877][INFO ][env ] [node01] using [1] data paths, mounts [[(C:)]], net usable_space [21.5gb], net total_space [49.8gb], types [NTFS] [2015-06-24 11:13:54,795][TRACE][rest.action.mongodb ] [node01] RestMongoDBRiverAction - baseUrl: /_river/mongodb [2015-06-24 11:13:55,028][INFO ][node ] [node01] initialized [2015-06-24 11:13:55,028][INFO ][node ] [node01] starting ... [2015-06-24 11:13:55,256][INFO ][transport ] [node01] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.41.108.209:9300]} [2015-06-24 11:13:55,393][INFO ][discovery ] [node01] esLaaS/QxbjbgH6TyGbR_8sEl87EQ [2015-06-24 11:13:59,171][INFO ][cluster.service ] [node01] new_master [node01][QxbjbgH6TyGbR_8sEl87EQ][RCM41VQPLAAPP02][inet[/10.41.108.209:9300]], reason: zen-disco-join (elected_as_master) [2015-06-24 11:13:59,329][INFO ][gateway ] [node01] recovered [5] indices into cluster_state [2015-06-24 11:13:59,400][INFO ][http ] [node01] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.41.108.209:9200]} [2015-06-24 11:13:59,400][INFO ][node ] [node01] started [2015-06-24 11:14:00,561][INFO ][river ] [node01] rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers [2015-06-24 11:14:00,572][TRACE][org.elasticsearch.river.mongodb.MongoDBRiver] Initializing river : [pla_dev_laas_event] [2015-06-24 11:14:00,573][TRACE][river.mongodb ] Parse river settings for pla_dev_laas_event [2015-06-24 11:14:00,580][TRACE][river.mongodb ] mongoServersSettings: [{port=27018, host=RCM41VHPLAAPP01}, {port=27018, host=RCM41VQPLAAPP01}, {port=27018, host=RCM41VQPLAAPP02}] [2015-06-24 11:14:00,580][TRACE][river.mongodb ] Server: RCM41VHPLAAPP01 - 27018 [2015-06-24 11:14:00,582][TRACE][river.mongodb ] Server: RCM41VQPLAAPP01 - 27018 [2015-06-24 11:14:00,582][TRACE][river.mongodb ] Server: RCM41VQPLAAPP02 - 27018 [2015-06-24 11:14:00,613][INFO ][org.elasticsearch.river.mongodb.MongoDBRiver] MongoDB River Plugin - version[2.0.9] - hash[73ddea5] - time[2015-04-06T21:16:46Z]

[2015-06-24 11:14:00,615][ERROR][org.elasticsearch.river.mongodb.MongoDBRiver] Cannot start river pla_dev_laas_event. Current status is START_FAILED

My MongoDB version is: 3.0.2. My ES version is: 1.6.0.

Here is my river definition:

C:\Utils\curl\bin>curl -XGET "rcm41vqplaapp02:9200/_river/pla_dev_laas_event/_meta" {"_index":"_river","_type":"pla_dev_laas_event","_id":"_meta","_version":3,"found":true,"_source":{ "type": "mongodb", "mongodb": { "servers": [ { "host": "RCM41VHPLAAPP01", "port": "27018" }, { "host": "RCM41VQPLAAPP01", "port": "27018" }, { "host": "RCM41VQPLAAPP02", "port": "27018" } ], "credentials": [ { "db": "LaaS", "user": "test", "password": "pswd" }, { "db": "admin", "user": "admin", "password": "pswd" } ], "db": "LaaS", "collection": "Event", "gridfs": false }, "index": { "name": "laas_event_index", "type": "event" } }

}

naveenann commented 9 years ago

I am having the same issue with ES 1.6

johnxjcheng commented 9 years ago

Yesterday I attempted it a few more times. Not sure what I have done helped it. But the river is working now. What I tried was adding/removing some meta data and restart ES. Here is my latest meta data:

C:\Utils\curl\bin>curl -XGET "rcm41vqplaapp02:9200/_river/pla_dev_laas_event/_meta" {"_index":"_river","_type":"pla_dev_laas_event","_id":"_meta","_version":8,"found":true,"_source":{ "type": "mongodb", "mongodb": { "servers": [ { "host": "RCM41VHPLAAPP01", "port": 27018 }, { "host": "RCM41VQPLAAPP01", "port": 27018 }, { "host": "RCM41VQPLAAPP02", "port": 27018 } ], "options": { "secondary_read_preference" : true }, "credentials": [ { "db": "admin", "user": "admin", "password": "pswd" } ], "db": "LaaS", "collection": "Event" }, "index": { "name": "laas_event_index", "type": "event" } } }