Yeah, could also be the cause when starting the cluster node after node. Any source code somewhere around where I can see how to make my SuggestService aware for moved shards?
Bernd Am Freitag, 21. November 2014 14:28:02 UTC+1 schrieb Jörg Prante: > > It seems there is a bug in > > de.ubbielefeld.elasticsearch.service.suggest.SuggestService > > which is not aware of a moved shard. > > Jörg > > On Fri, Nov 21, 2014 at 2:14 PM, Bernd Fehling <[email protected] > <javascript:>> wrote: > >> I have a cluster with four shards with one replica. >> Each master is with one replica in one java instance. >> >> Any idea what can cause this warning? >> [WARN ][indices ] [node_01] [myindex][0] failed to >> invoke before shard closed callback >> org.elasticsearch.index.IndexShardMissingException: [myindex][0] missing >> at >> org.elasticsearch.index.service.InternalIndexService.shardInjectorSafe(InternalIndexService.java:292) >> at >> de.ubbielefeld.elasticsearch.service.suggest.SuggestService$2.beforeIndexShardClosed(SuggestService.java:74) >> at >> org.elasticsearch.indices.InternalIndicesLifecycle.beforeIndexShardClosed(InternalIndicesLifecycle.java:148) >> at >> org.elasticsearch.index.service.InternalIndexService.removeShard(InternalIndexService.java:376) >> at >> org.elasticsearch.indices.cluster.IndicesClusterStateService.applyDeletedShards(IndicesClusterStateService.java:287) >> at >> org.elasticsearch.indices.cluster.IndicesClusterStateService.clusterChanged(IndicesClusterStateService.java:183) >> at >> org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:424) >> at >> org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:134) >> 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) >> >> May be a timeout somewhere? >> >> I see the warning when starting the cluster, but also when rerouting a >> shard from one node to another. >> >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/9972730b-b862-4a2c-aed4-4da2ad85ec6d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/9972730b-b862-4a2c-aed4-4da2ad85ec6d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8505ed9e-c175-4f1c-bd87-35ddf478b1cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
