im trying to create custom river plugin and im getting this error after
starting cluster:
Aug 29, 2013 4:55:02 PM river.routing
WARNING: [Grant, Greer] failed to get/parse _meta for [cc_river]
org.elasticsearch.index.shard.IllegalIndexShardStateException: [_river][0]
CurrentState[RECOVERING] Read operations only allowed when started/relocated
at
org.elasticsearch.index.shard.service.InternalIndexShard.readAllowed(InternalIndexShard.java:686)
at
org.elasticsearch.index.shard.service.InternalIndexShard.get(InternalIndexShard.java:410)
at
org.elasticsearch.index.get.ShardGetService.innerGet(ShardGetService.java:194)
at org.elasticsearch.index.get.ShardGetService.get(ShardGetService.java:105)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:102)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:42)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:160)
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:722)
looks like there is some racing condition between index recovering and
reading river metadata
(when i slow down my plugin initialization with thread.sleep im not getting
this error)
any suggestion what i may be doing wrong there ?
my default index settings:
index.number_of_shards: 1
index.number_of_replicas: 0
+1 I've run into this issue as well and it appears a couple others have as
well as I found an open bug for it:
On Thursday, August 29, 2013 9:13:38 AM UTC-7, Karol Gwaj wrote:
Hi Guys,
im trying to create custom river plugin and im getting this error after
starting cluster:
Aug 29, 2013 4:55:02 PM river.routing
WARNING: [Grant, Greer] failed to get/parse _meta for [cc_river]
org.elasticsearch.index.shard.IllegalIndexShardStateException: [_river][0]
CurrentState[RECOVERING] Read operations only allowed when started/relocated
at
org.elasticsearch.index.shard.service.InternalIndexShard.readAllowed(InternalIndexShard.java:686)
at
org.elasticsearch.index.shard.service.InternalIndexShard.get(InternalIndexShard.java:410)
at
org.elasticsearch.index.get.ShardGetService.innerGet(ShardGetService.java:194)
at
org.elasticsearch.index.get.ShardGetService.get(ShardGetService.java:105)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:102)
at
org.elasticsearch.action.get.TransportGetAction.shardOperation(TransportGetAction.java:42)
at
org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction$1.run(TransportShardSingleOperationAction.java:160)
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:722)
looks like there is some racing condition between index recovering and
reading river metadata
(when i slow down my plugin initialization with thread.sleep im not
getting this error)
any suggestion what i may be doing wrong there ?
my default index settings:
index.number_of_shards: 1
index.number_of_replicas: 0
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.