# River errors on elasticsearch restart **URL:** \ **Category:** Elasticsearch\ **Created:** [August 28, 2013, 4:37am UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357 "2013-08-28T04:37:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![11126](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/11126/32/2141_2.png) [@11126](https://discuss.elastic.co/u/11126)\ **Post date:** [August 28, 2013, 4:37am UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/1 "2013-08-28T04:37:10Z")
Hi, There are some errors on elasticsearch restart. Full log on github issue > After several messages river and elasticsearch worked fine. What produces a these errors? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [September 12, 2013, 9:51am UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/2 "2013-09-12T09:51:46Z")
Hey, I am somewhat unsure what is happening here. I just want to make sure it is reproducible in order to take a look at. 1. Delete river config (please provide the curl call) 2. Add river config (please provide the curl call) 3. Stop elasticsearch 4. Start elasticsearch 5. See exception... Does it work that way, or am I missing something? Thanks for helping out! --Alex On Wed, Aug 28, 2013 at 6:37 AM, Евгений Власенко [mahnunchik@gmail.com](mailto:mahnunchik@gmail.com)wrote: > Hi, > > There are some errors on elasticsearch restart. > Full log on github issue > [Errors on restart - NoShardAvailableActionException · Issue #120 · richardwilly98/elasticsearch-river-mongodb · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/120) > After several messages river and elasticsearch worked fine. > What produces a these errors? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Steven\_Brent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steven_brent/32/2103_2.png) [@Steven\_Brent](https://discuss.elastic.co/u/Steven_Brent)\ **Post date:** [September 16, 2013, 4:47pm UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/3 "2013-09-16T16:47:04Z")
I'm having the same issue (or similar?) issue. Here is the version information for everything: _MongoDB:_ 2.4.3 _ES:_ 0.90.3 _elasticsearch-river-mongodb:_ 1.7.0 One thing I noticed is that according to rs.conf() in the Mongo shell, the replica set host config is using the local machine name (e.g. 'Steven's Thing:27017') rather than the loopback address. I mean, it's all up and running and everything is talking to each other so maybe that doesn't matter - or maybe rivers need those to match? At any rate, here is the shell script I used to create a river for my test collection ('blog'): #!/bin/sh curl -XPUT "localhost:9200/\_river/mongoblog/\_meta" -d ' { "type": "mongodb", "mongodb": { "servers": [ { "host": "127.0.0.1", "port": 27017 } ], "options": { "secondary\_read\_preference": true }, "db": "blog", "collection": "users" }, "index": { "name": "usersidx", "type": "users" }}' And here is the curl call I use to delete that river config: curl -XDELETE '[http://localhost:9200/\_river/mongoblog](http://localhost:9200/_river/mongoblog)' When I first create the river, all the indexing works fine, I can add new documents in Mongo and they get slurped right up and search work as expected. On restarting ES though, I get the following: [2013-09-16 12:31:01,444][INFO][node] [Bob Diamond]started [2013-09-16 12:31:01,457][DEBUG][action.get] [Bob Diamond] [ \_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null]] org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] null at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction$AsyncSingleAction.start( TransportShardSingleOperationAction.java:123) at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction.doExecute( TransportShardSingleOperationAction.java:72) at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction.doExecute( TransportShardSingleOperationAction.java:47) at org.elasticsearch.action.support.TransportAction.execute(TransportAction .java:61) at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java: 179) at org.elasticsearch.action.get.GetRequestBuilder.doExecute( GetRequestBuilder.java:112) at org.elasticsearch.action.ActionRequestBuilder.execute( ActionRequestBuilder.java:85) at org.elasticsearch.action.ActionRequestBuilder.execute( ActionRequestBuilder.java:59) at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter.java :109) at org.elasticsearch.river.cluster.RiverClusterService$1.run( RiverClusterService.java:103) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:918) at java.lang.Thread.run(Thread.java:680) [2013-09-16 12:31:01,854][INFO][gateway] [Bob Diamond]recovered [2] indices into cluster\_state [2013-09-16 12:31:01,858][DEBUG][action.get] [Bob Diamond] [ \_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null]] org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] null at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction$AsyncSingleAction.start( TransportShardSingleOperationAction.java:123) at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction.doExecute( TransportShardSingleOperationAction.java:72) at org.elasticsearch.action.support.single.shard. TransportShardSingleOperationAction.doExecute( TransportShardSingleOperationAction.java:47) at org.elasticsearch.action.support.TransportAction.execute(TransportAction .java:61) at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java: 179) at org.elasticsearch.action.get.GetRequestBuilder.doExecute( GetRequestBuilder.java:112) at org.elasticsearch.action.ActionRequestBuilder.execute( ActionRequestBuilder.java:85) at org.elasticsearch.action.ActionRequestBuilder.execute( ActionRequestBuilder.java:59) at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter.java :109) at org.elasticsearch.river.cluster.RiverClusterService$1.run( RiverClusterService.java:103) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:918) at java.lang.Thread.run(Thread.java:680) I haven't issues in userland yet, but this kind of stuff makes me nervous. Thanks for any help! On Thursday, September 12, 2013 5:51:46 AM UTC-4, Alexander Reelsen wrote: > Hey, > > I am somewhat unsure what is happening here. I just want to make sure it > is reproducible in order to take a look at. > > 1. Delete river config (please provide the curl call) > 2. Add river config (please provide the curl call) > 3. Stop elasticsearch > 4. Start elasticsearch > 5. See exception... > > Does it work that way, or am I missing something? > > Thanks for helping out! > > --Alex > > On Wed, Aug 28, 2013 at 6:37 AM, Евгений Власенко \<[mahnu...@gmail.com](mailto:mahnu...@gmail.com)\ > > > wrote: > > > Hi, > > > > There are some errors on elasticsearch restart. > > Full log on github issue > > [Errors on restart - NoShardAvailableActionException · Issue #120 · richardwilly98/elasticsearch-river-mongodb · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/120) > > After several messages river and elasticsearch worked fine. > > What produces a these errors? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Steven\_Brent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steven_brent/32/2103_2.png) [@Steven\_Brent](https://discuss.elastic.co/u/Steven_Brent)\ **Post date:** [September 16, 2013, 5:06pm UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/4 "2013-09-16T17:06:40Z")
Here's my full MongoDB replication set status, in case that matters: { "set" : "rs0", "date" : { "$date" : "Mon Sep 16 13:05:18 2013" }, "myState" : 1, "members" : [ { "\_id" : 0, "name" : "Stevens-MacBook-Pro.local:27017", "health" : 1, "state" : 1, "stateStr" : "PRIMARY", "uptime" : 11, "optime" : { "$timestamp" : { "t" : 1379347350, "i" : 1 } }, "optimeDate" : { "$date" : "Mon Sep 16 12:02:30 2013" }, "self" : true } ], "ok" : 1 } On Monday, September 16, 2013 12:47:04 PM UTC-4, Steven Brent wrote: > I'm having the same issue (or similar?) issue. > > Here is the version information for everything: > > _MongoDB:_ 2.4.3 > _ES:_ 0.90.3 > _elasticsearch-river-mongodb:_ 1.7.0 > > One thing I noticed is that according to rs.conf() in the Mongo shell, the > replica set host config is using the local machine name (e.g. 'Steven's > Thing:27017') rather than the loopback address. I mean, it's all up and > running and everything is talking to each other so maybe that doesn't > matter - or maybe rivers need those to match? > > At any rate, here is the shell script I used to create a river for my test > collection ('blog'): > > #!/bin/sh > curl -XPUT "localhost:9200/\_river/mongoblog/\_meta" -d ' > { > "type": "mongodb", > "mongodb": { > "servers": [ > { "host": "127.0.0.1", "port": 27017 } > ], > "options": { "secondary\_read\_preference": true }, > "db": "blog", > "collection": "users" > }, > "index": { > "name": "usersidx", > "type": "users" > }}' > > And here is the curl call I use to delete that river config: > > curl -XDELETE '[http://localhost:9200/\_river/mongoblog](http://localhost:9200/_river/mongoblog)' > > When I first create the river, all the indexing works fine, I can add new > documents in Mongo and they get slurped right up and search work as > expected. On restarting ES though, I get the following: > > [2013-09-16 12:31:01,444][INFO][node] [Bob Diamond]started > [2013-09-16 12:31:01,457][DEBUG][action.get] [Bob Diamond] > [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null > ]] > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] null > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction$AsyncSingleAction.start( > TransportShardSingleOperationAction.java:123) > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction.doExecute( > TransportShardSingleOperationAction.java:72) > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction.doExecute( > TransportShardSingleOperationAction.java:47) > at org.elasticsearch.action.support.TransportAction.execute( > TransportAction.java:61) > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > java:179) > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > GetRequestBuilder.java:112) > at org.elasticsearch.action.ActionRequestBuilder.execute( > ActionRequestBuilder.java:85) > at org.elasticsearch.action.ActionRequestBuilder.execute( > ActionRequestBuilder.java:59) > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > java:109) > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > RiverClusterService.java:103) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. > java:918) > at java.lang.Thread.run(Thread.java:680) > [2013-09-16 12:31:01,854][INFO][gateway] [Bob Diamond]recovered > [2] indices into cluster\_state > [2013-09-16 12:31:01,858][DEBUG][action.get] [Bob Diamond] > [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null > ]] > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] null > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction$AsyncSingleAction.start( > TransportShardSingleOperationAction.java:123) > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction.doExecute( > TransportShardSingleOperationAction.java:72) > at org.elasticsearch.action.support.single.shard. > TransportShardSingleOperationAction.doExecute( > TransportShardSingleOperationAction.java:47) > at org.elasticsearch.action.support.TransportAction.execute( > TransportAction.java:61) > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > java:179) > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > GetRequestBuilder.java:112) > at org.elasticsearch.action.ActionRequestBuilder.execute( > ActionRequestBuilder.java:85) > at org.elasticsearch.action.ActionRequestBuilder.execute( > ActionRequestBuilder.java:59) > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > java:109) > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > RiverClusterService.java:103) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. > java:918) > at java.lang.Thread.run(Thread.java:680) > > I haven't issues in userland yet, but this kind of stuff makes me nervous. > Thanks for any help! > > On Thursday, September 12, 2013 5:51:46 AM UTC-4, Alexander Reelsen wrote: > > > Hey, > > > > I am somewhat unsure what is happening here. I just want to make sure it > > is reproducible in order to take a look at. > > > > 1. Delete river config (please provide the curl call) > > 2. Add river config (please provide the curl call) > > 3. Stop elasticsearch > > 4. Start elasticsearch > > 5. See exception... > > > > Does it work that way, or am I missing something? > > > > Thanks for helping out! > > > > --Alex > > > > On Wed, Aug 28, 2013 at 6:37 AM, Евгений Власенко [mahnu...@gmail.com](mailto:mahnu...@gmail.com)wrote: > > > > > Hi, > > > > > > There are some errors on elasticsearch restart. > > > Full log on github issue > > > [Errors on restart - NoShardAvailableActionException · Issue #120 · richardwilly98/elasticsearch-river-mongodb · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/120) > > > After several messages river and elasticsearch worked fine. > > > What produces a these errors? > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Steven\_Brent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steven_brent/32/2103_2.png) [@Steven\_Brent](https://discuss.elastic.co/u/Steven_Brent)\ **Post date:** [September 20, 2013, 1:01pm UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/5 "2013-09-20T13:01:28Z")
Bump 🙂 On Monday, September 16, 2013 1:06:40 PM UTC-4, Steven Brent wrote: > Here's my full MongoDB replication set status, in case that matters: > > { "set" : "rs0", > "date" : { "$date" : "Mon Sep 16 13:05:18 2013" }, > "myState" : 1, > "members" : [ > { "\_id" : 0, > "name" : "Stevens-MacBook-Pro.local:27017", > "health" : 1, > "state" : 1, > "stateStr" : "PRIMARY", > "uptime" : 11, > "optime" : { "$timestamp" : { "t" : 1379347350, "i" : 1 } }, > "optimeDate" : { "$date" : "Mon Sep 16 12:02:30 2013" }, > "self" : true } ], > "ok" : 1 } > > On Monday, September 16, 2013 12:47:04 PM UTC-4, Steven Brent wrote: > > > I'm having the same issue (or similar?) issue. > > > > Here is the version information for everything: > > > > _MongoDB:_ 2.4.3 > > _ES:_ 0.90.3 > > _elasticsearch-river-mongodb:_ 1.7.0 > > > > One thing I noticed is that according to rs.conf() in the Mongo shell, > > the replica set host config is using the local machine name (e.g. 'Steven's > > Thing:27017') rather than the loopback address. I mean, it's all up and > > running and everything is talking to each other so maybe that doesn't > > matter - or maybe rivers need those to match? > > > > At any rate, here is the shell script I used to create a river for my > > test collection ('blog'): > > > > #!/bin/sh > > curl -XPUT "localhost:9200/\_river/mongoblog/\_meta" -d ' > > { > > "type": "mongodb", > > "mongodb": { > > "servers": [ > > { "host": "127.0.0.1", "port": 27017 } > > ], > > "options": { "secondary\_read\_preference": true }, > > "db": "blog", > > "collection": "users" > > }, > > "index": { > > "name": "usersidx", > > "type": "users" > > }}' > > > > And here is the curl call I use to delete that river config: > > > > curl -XDELETE '[http://localhost:9200/\_river/mongoblog](http://localhost:9200/_river/mongoblog)' > > > > When I first create the river, all the indexing works fine, I can add new > > documents in Mongo and they get slurped right up and search work as > > expected. On restarting ES though, I get the following: > > > > [2013-09-16 12:31:01,444][INFO][node] [Bob Diamond]started > > [2013-09-16 12:31:01,457][DEBUG][action.get] [Bob Diamond] > > [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null > > ]] > > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] > > null > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction$AsyncSingleAction.start( > > TransportShardSingleOperationAction.java:123) > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction.doExecute( > > TransportShardSingleOperationAction.java:72) > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction.doExecute( > > TransportShardSingleOperationAction.java:47) > > at org.elasticsearch.action.support.TransportAction.execute( > > TransportAction.java:61) > > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > > java:179) > > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > > GetRequestBuilder.java:112) > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > ActionRequestBuilder.java:85) > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > ActionRequestBuilder.java:59) > > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > > java:109) > > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > > RiverClusterService.java:103) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > > ThreadPoolExecutor.java:895) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > > .java:918) > > at java.lang.Thread.run(Thread.java:680) > > [2013-09-16 12:31:01,854][INFO][gateway] [Bob Diamond]recovered > > [2] indices into cluster\_state > > [2013-09-16 12:31:01,858][DEBUG][action.get] [Bob Diamond] > > [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [null > > ]] > > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] > > null > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction$AsyncSingleAction.start( > > TransportShardSingleOperationAction.java:123) > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction.doExecute( > > TransportShardSingleOperationAction.java:72) > > at org.elasticsearch.action.support.single.shard. > > TransportShardSingleOperationAction.doExecute( > > TransportShardSingleOperationAction.java:47) > > at org.elasticsearch.action.support.TransportAction.execute( > > TransportAction.java:61) > > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > > java:179) > > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > > GetRequestBuilder.java:112) > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > ActionRequestBuilder.java:85) > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > ActionRequestBuilder.java:59) > > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > > java:109) > > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > > RiverClusterService.java:103) > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > > ThreadPoolExecutor.java:895) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > > .java:918) > > at java.lang.Thread.run(Thread.java:680) > > > > I haven't issues in userland yet, but this kind of stuff makes me > > nervous. Thanks for any help! > > > > On Thursday, September 12, 2013 5:51:46 AM UTC-4, Alexander Reelsen wrote: > > > > > Hey, > > > > > > I am somewhat unsure what is happening here. I just want to make sure it > > > is reproducible in order to take a look at. > > > > > > 1. Delete river config (please provide the curl call) > > > 2. Add river config (please provide the curl call) > > > 3. Stop elasticsearch > > > 4. Start elasticsearch > > > 5. See exception... > > > > > > Does it work that way, or am I missing something? > > > > > > Thanks for helping out! > > > > > > --Alex > > > > > > On Wed, Aug 28, 2013 at 6:37 AM, Евгений Власенко [mahnu...@gmail.com](mailto:mahnu...@gmail.com)wrote: > > > > > > > Hi, > > > > > > > > There are some errors on elasticsearch restart. > > > > Full log on github issue > > > > [Errors on restart - NoShardAvailableActionException · Issue #120 · richardwilly98/elasticsearch-river-mongodb · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/120) > > > > After several messages river and elasticsearch worked fine. > > > > What produces a these errors? > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![benmccann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benmccann/32/420_2.png) [@benmccann](https://discuss.elastic.co/u/benmccann)\ **Post date:** [September 24, 2013, 3:40am UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/6 "2013-09-24T03:40:51Z")
+1 I've found a few other people with this issue as well: > > > When a river \[1\] has been registered and ES is restarted. > I keep getting the fol…lowing exception in the log: > \[2013-09-10 10:22:55,066\]\[INFO \]\[node \] \[Box IV\] version\[0.90.3\], pid\[26144\], build\[5c38d60/2013-08-06T13:18:31Z\] > \[2013-09-10 10:22:55,067\]\[INFO \]\[node \] \[Box IV\] initializing ... > \[2013-09-10 10:22:55,115\]\[INFO \]\[plugins \] \[Box IV\] loaded \[mongodb-river, mapper-attachments, lang-groovy, lang-javascript\], sites \[river-mongodb, head\] > \[2013-09-10 10:22:58,456\]\[INFO \]\[node \] \[Box IV\] initialized > \[2013-09-10 10:22:58,456\]\[INFO \]\[node \] \[Box IV\] starting ... > \[2013-09-10 10:22:59,639\]\[INFO \]\[transport \] \[Box IV\] bound\_address {inet\[/0:0:0:0:0:0:0:0:9300\]}, publish\_address {inet\[/192.168.1.117:9300\]} > \[2013-09-10 10:23:03,145\]\[INFO \]\[cluster.service \] \[Box IV\] new\_master \[Box IV\]\[AllhKDYIScKfW8Ue1YcmQw\]\[inet\[/192.168.1.117:9300\]\], reason: zen-disco-join (elected\_as\_master) > \[2013-09-10 10:23:03,169\]\[INFO \]\[discovery \] \[Box IV\] elasticsearch/AllhKDYIScKfW8Ue1YcmQw > \[2013-09-10 10:23:03,216\]\[DEBUG\]\[action.get \] \[Box IV\] \[\_river\]\[0\]: failed to execute \[\[\_river\]\[river101\]\[\_meta\]: routing \[null\]\] > org.elasticsearch.action.NoShardAvailableActionException: \[\_river\]\[0\] null > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.start(TransportShardSingleOperationAction.java:123) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:72) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:47) > at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:61) > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java:179) > at org.elasticsearch.action.get.GetRequestBuilder.doExecute(GetRequestBuilder.java:112) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59) > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter.java:109) > at org.elasticsearch.river.cluster.RiverClusterService$1.run(RiverClusterService.java:103) > 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) > \[2013-09-10 10:23:03,683\]\[INFO \]\[gateway \] \[Box IV\] recovered \[7\] indices into cluster\_state > \[2013-09-10 10:23:03,702\]\[DEBUG\]\[action.get \] \[Box IV\] \[\_river\]\[0\]: failed to execute \[\[\_river\]\[river101\]\[\_meta\]: routing \[null\]\] > org.elasticsearch.action.NoShardAvailableActionException: \[\_river\]\[0\] null > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.start(TransportShardSingleOperationAction.java:123) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:72) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:47) > at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:61) > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java:179) > at org.elasticsearch.action.get.GetRequestBuilder.doExecute(GetRequestBuilder.java:112) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59) > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter.java:109) > at org.elasticsearch.river.cluster.RiverClusterService$1.run(RiverClusterService.java:103) > 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) > \[2013-09-10 10:23:03,849\]\[DEBUG\]\[action.get \] \[Box IV\] \[\_river\]\[0\]: failed to execute \[\[\_river\]\[river101\]\[\_meta\]: routing \[null\]\] > org.elasticsearch.action.NoShardAvailableActionException: \[\_river\]\[0\] null > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.start(TransportShardSingleOperationAction.java:123) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:72) > at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:47) > at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:61) > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java:179) > at org.elasticsearch.action.get.GetRequestBuilder.doExecute(GetRequestBuilder.java:112) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85) > at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59) > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter.java:109) > at org.elasticsearch.river.cluster.RiverClusterService$1.run(RiverClusterService.java:103) > 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) > > The same plugin version works without this exception in ES 0.90.2. Even with the exception data are correctly imported in ES by the river. > > \[1\] - https://github.com/richardwilly98/elasticsearch-river-mongodb On Friday, September 20, 2013 6:01:28 AM UTC-7, Steven Brent wrote: > Bump 🙂 > > On Monday, September 16, 2013 1:06:40 PM UTC-4, Steven Brent wrote: > > > Here's my full MongoDB replication set status, in case that matters: > > > > { "set" : "rs0", > > "date" : { "$date" : "Mon Sep 16 13:05:18 2013" }, > > "myState" : 1, > > "members" : [ > > { "\_id" : 0, > > "name" : "Stevens-MacBook-Pro.local:27017", > > "health" : 1, > > "state" : 1, > > "stateStr" : "PRIMARY", > > "uptime" : 11, > > "optime" : { "$timestamp" : { "t" : 1379347350, "i" : 1 } }, > > "optimeDate" : { "$date" : "Mon Sep 16 12:02:30 2013" }, > > "self" : true } ], > > "ok" : 1 } > > > > On Monday, September 16, 2013 12:47:04 PM UTC-4, Steven Brent wrote: > > > > > I'm having the same issue (or similar?) issue. > > > > > > Here is the version information for everything: > > > > > > _MongoDB:_ 2.4.3 > > > _ES:_ 0.90.3 > > > _elasticsearch-river-mongodb:_ 1.7.0 > > > > > > One thing I noticed is that according to rs.conf() in the Mongo shell, > > > the replica set host config is using the local machine name (e.g. 'Steven's > > > Thing:27017') rather than the loopback address. I mean, it's all up and > > > running and everything is talking to each other so maybe that doesn't > > > matter - or maybe rivers need those to match? > > > > > > At any rate, here is the shell script I used to create a river for my > > > test collection ('blog'): > > > > > > #!/bin/sh > > > curl -XPUT "localhost:9200/\_river/mongoblog/\_meta" -d ' > > > { > > > "type": "mongodb", > > > "mongodb": { > > > "servers": [ > > > { "host": "127.0.0.1", "port": 27017 } > > > ], > > > "options": { "secondary\_read\_preference": true }, > > > "db": "blog", > > > "collection": "users" > > > }, > > > "index": { > > > "name": "usersidx", > > > "type": "users" > > > }}' > > > > > > And here is the curl call I use to delete that river config: > > > > > > curl -XDELETE '[http://localhost:9200/\_river/mongoblog](http://localhost:9200/_river/mongoblog)' > > > > > > When I first create the river, all the indexing works fine, I can add > > > new documents in Mongo and they get slurped right up and search work as > > > expected. On restarting ES though, I get the following: > > > > > > [2013-09-16 12:31:01,444][INFO][node] [Bob Diamond > > > ] started > > > [2013-09-16 12:31:01,457][DEBUG][action.get] [Bob Diamond > > > ] [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [ > > > null]] > > > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] > > > null > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction$AsyncSingleAction.start( > > > TransportShardSingleOperationAction.java:123) > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction.doExecute( > > > TransportShardSingleOperationAction.java:72) > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction.doExecute( > > > TransportShardSingleOperationAction.java:47) > > > at org.elasticsearch.action.support.TransportAction.execute( > > > TransportAction.java:61) > > > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > > > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > > > java:179) > > > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > > > GetRequestBuilder.java:112) > > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > > ActionRequestBuilder.java:85) > > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > > ActionRequestBuilder.java:59) > > > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > > > java:109) > > > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > > > RiverClusterService.java:103) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > > > ThreadPoolExecutor.java:895) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > ThreadPoolExecutor.java:918) > > > at java.lang.Thread.run(Thread.java:680) > > > [2013-09-16 12:31:01,854][INFO][gateway] [Bob Diamond > > > ] recovered [2] indices into cluster\_state > > > [2013-09-16 12:31:01,858][DEBUG][action.get] [Bob Diamond > > > ] [\_river][0]: failed to execute [[\_river][mongoblog][\_meta]: routing [ > > > null]] > > > org.elasticsearch.action.NoShardAvailableActionException: [\_river][0] > > > null > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction$AsyncSingleAction.start( > > > TransportShardSingleOperationAction.java:123) > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction.doExecute( > > > TransportShardSingleOperationAction.java:72) > > > at org.elasticsearch.action.support.single.shard. > > > TransportShardSingleOperationAction.doExecute( > > > TransportShardSingleOperationAction.java:47) > > > at org.elasticsearch.action.support.TransportAction.execute( > > > TransportAction.java:61) > > > at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92) > > > at org.elasticsearch.client.support.AbstractClient.get(AbstractClient. > > > java:179) > > > at org.elasticsearch.action.get.GetRequestBuilder.doExecute( > > > GetRequestBuilder.java:112) > > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > > ActionRequestBuilder.java:85) > > > at org.elasticsearch.action.ActionRequestBuilder.execute( > > > ActionRequestBuilder.java:59) > > > at org.elasticsearch.river.routing.RiversRouter$1.execute(RiversRouter. > > > java:109) > > > at org.elasticsearch.river.cluster.RiverClusterService$1.run( > > > RiverClusterService.java:103) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( > > > ThreadPoolExecutor.java:895) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > ThreadPoolExecutor.java:918) > > > at java.lang.Thread.run(Thread.java:680) > > > > > > I haven't issues in userland yet, but this kind of stuff makes me > > > nervous. Thanks for any help! > > > > > > On Thursday, September 12, 2013 5:51:46 AM UTC-4, Alexander Reelsen > > > wrote: > > > > > > > Hey, > > > > > > > > I am somewhat unsure what is happening here. I just want to make sure > > > > it is reproducible in order to take a look at. > > > > > > > > 1. Delete river config (please provide the curl call) > > > > 2. Add river config (please provide the curl call) > > > > 3. Stop elasticsearch > > > > 4. Start elasticsearch > > > > 5. See exception... > > > > > > > > Does it work that way, or am I missing something? > > > > > > > > Thanks for helping out! > > > > > > > > --Alex > > > > > > > > On Wed, Aug 28, 2013 at 6:37 AM, Евгений Власенко [mahnu...@gmail.com](mailto:mahnu...@gmail.com)wrote: > > > > > > > > > Hi, > > > > > > > > > > There are some errors on elasticsearch restart. > > > > > Full log on github issue > > > > > [Errors on restart - NoShardAvailableActionException · Issue #120 · richardwilly98/elasticsearch-river-mongodb · GitHub](https://github.com/richardwilly98/elasticsearch-river-mongodb/issues/120) > > > > > After several messages river and elasticsearch worked fine. > > > > > What produces a these errors? > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:14am UTC](https://discuss.elastic.co/t/river-errors-on-elasticsearch-restart/13357/7 "2017-07-06T02:14:58Z")