Everything was working fine when all of a sudden some indices started
failing.
GET localhost:9200/logstash-2014.09.11/_search
yields response:
{"error":"SearchPhaseExecutionException[Failed to execute phase [query],
all shards failed]","status":503}
Everything was working fine when all of a sudden some indices started
failing.
GET localhost:9200/logstash-2014.09.11/_search
yields response:
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query], all shards failed]","status":503}
How's the cluster's health? Anything interesting in the Elasticsearch
logs?
--
Magnus Bäck | Software Engineer, Development Tools magnus.back@sonymobile.com | Sony Mobile Communications
On Friday, September 12, 2014 2:57:06 AM UTC-4, Magnus Bäck wrote:
On Friday, September 12, 2014 at 08:53 CEST,
Kevin DeLand <kevin....@gmail.com <javascript:>> wrote:
Everything was working fine when all of a sudden some indices started
failing.
GET localhost:9200/logstash-2014.09.11/_search
yields response:
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query], all shards failed]","status":503}
How's the cluster's health? Anything interesting in the Elasticsearch
logs?
--
Magnus Bäck | Software Engineer, Development Tools magnu...@sonymobile.com <javascript:> | Sony Mobile Communications
From
*~/elasticsearch-1.3.1/logs/elasticsearch.log *
[2014-09-12 07:17:26,047][DEBUG][action.bulk ] [Frankie and
Victoria] observer: timeout notification from cluster service. timeout
setting [1m], time since start [1m]
[2014-09-12 07:18:04,466][DEBUG][action.search.type ] [Frankie and
Victoria] All shards failed for phase: [query]
[2014-09-12 07:18:27,103][DEBUG][action.bulk ] [Frankie and
Victoria] observer: timeout notification from cluster service. timeout
setting [1m], time since start [1m]
[2014-09-12 07:18:27,103][DEBUG][action.bulk ] [Frankie and
Victoria] observer: timeout notification from cluster service. timeout
setting [1m], time since start [1m]
On Friday, September 12, 2014 2:57:06 AM UTC-4, Magnus Bäck wrote:
On Friday, September 12, 2014 at 08:53 CEST,
Kevin DeLand <kevin....@gmail.com <javascript:>> wrote:
Everything was working fine when all of a sudden some indices started
failing.
GET localhost:9200/logstash-2014.09.11/_search
yields response:
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query], all shards failed]","status":503}
How's the cluster's health? Anything interesting in the Elasticsearch
logs?
--
Magnus Bäck | Software Engineer, Development Tools magnu...@sonymobile.com <javascript:> | Sony Mobile Communications
There are six indices with a red cluster status, but only two fail... any
advice on what to check?
On Friday, September 12, 2014 2:57:06 AM UTC-4, Magnus Bäck wrote:
On Friday, September 12, 2014 at 08:53 CEST,
Kevin DeLand <kevin....@gmail.com <javascript:>> wrote:
Everything was working fine when all of a sudden some indices started
failing.
GET localhost:9200/logstash-2014.09.11/_search
yields response:
{"error":"SearchPhaseExecutionException[Failed to execute phase
[query], all shards failed]","status":503}
How's the cluster's health? Anything interesting in the Elasticsearch
logs?
--
Magnus Bäck | Software Engineer, Development Tools magnu...@sonymobile.com <javascript:> | Sony Mobile Communications
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.