Hey,
can you reliably recreate this? And try to create a gist? Preferrably, when
using elasticsearch 0.90.9. When you create an index, you usually create 5
shards, so, how can 3/4 shards be corrupt? Did you change anything and do
not use the defaults (are you changing the defaults somewhere else as
well)? It would be great if you could provide a reproducible example using
a gist, like mentioned in Elasticsearch Platform — Find real-time answers at scale | Elastic
--Alex
On Wed, Dec 25, 2013 at 4:35 PM, Tarang Dawer tarang.dawer@gmail.comwrote:
Hi all
I am facing an issue of corrupt index creation, whenever the es node is
killed just after the index is created. When the node is restarted, the
index shows 3/4 shards corrupt, with 503 status, which never recover, and
as a result, my indexing gets stuck. I am doing this on a single node, with
es version 90.1 . Please help me out.Thanks
Tarang Dawer--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEGWFQVihK%3DzJ9wE%2BzufhOSoOHg97g-FM6FFnqtw8JCpYO4VCQ%40mail.gmail.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM-ggGZXBRj_LwNc0ksEg-dcRDTZ-bKH_9AqJmOLi9A4UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.