River errors on elasticsearch restart


(Евгений Власенко) #1

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.
For more options, visit https://groups.google.com/groups/opt_out.


(Alexander Reelsen) #2

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.comwrote:

Hi,

There are some errors on elasticsearch restart.
Full log on github issue
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(Steven Brent) #3

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'

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<javascript:>

wrote:

Hi,

There are some errors on elasticsearch restart.
Full log on github issue
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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(Steven Brent) #4

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'

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.comwrote:

Hi,

There are some errors on elasticsearch restart.
Full log on github issue
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(Steven Brent) #5

Bump :slight_smile:

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'

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.comwrote:

Hi,

There are some errors on elasticsearch restart.
Full log on github issue
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(Ben McCann) #6

+1 I've found a few other people with this issue as well:

On Friday, September 20, 2013 6:01:28 AM UTC-7, Steven Brent wrote:

Bump :slight_smile:

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'

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.comwrote:

Hi,

There are some errors on elasticsearch restart.
Full log on github issue
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #7