The following as suggested was able to fix all my previous indexes to make
0 replication and essentially removing the 5 unassigned shards we had per
Indice.
curl -XPUT 'localhost:9200/*/_settings' -d ' { index : {
number_of_replicas : 0 } } '
Thank you.
--
You received this message
I didn't get any help on this but as an FYI for those that may have this
issue and are just starting:
Digging deeper it appears our system was created with 5 shards and 1
replica. Granted we are only using 1 node so every day elasticsearch
would create an indice of 10 shards, 5 for the
You should be able to set the number of replicas for all previous indexes
to 0. You cannot reduce the shard count once an index is created, or
increase for that matter. You could reindex your shards.
http://www.elastic.co/guide/en/elasticsearch/reference/current/indices-update-settings.html
Hello, have fixed it? What was the problem?
--
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+unsubscr...@googlegroups.com.
To view this discussion
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}
--
You received this message because you are
On Friday, September 12, 2014 at 08:53 CEST,
Kevin DeLand kevin.del...@gmail.com 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
Cluster health is red:
https://gist.github.com/kevindeland/2d727c3d984139ab96d4
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
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
