Missing SegmentInfo files after upgrade question (Issue 7430)

Elastic Stack Elasticsearch
1

Hey all,
I ran exactly into this issue
https://github.com/elasticsearch/elasticsearch/issues/7430, probably
because some time back, we upgraded from 0.20.5 directly to 1.2.2. My
question is, so now one of my indices (just one shard really) is missing
the SegmentInfo file. Is there a way to recreate them? Or am I screwed?
Is there a way to even preserve the data from the other shards of the same
index that did not encounter the issue?

-- Kris.

--
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/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

That one shard is likely hosed.

But if you a good replica of that shard then you may be able to delete the
hosed shard and let ES recover from the good one.

Or restore from snapshot...

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:13 PM, krispyjala krispyjala@gmail.com wrote:

Hey all,
I ran exactly into this issue
Internal: Indexes unuseable after upgrade from 0.2 to 1.3 and cluster restart · Issue #7430 · elastic/elasticsearch · GitHub, probably
because some time back, we upgraded from 0.20.5 directly to 1.2.2. My
question is, so now one of my indices (just one shard really) is missing
the SegmentInfo file. Is there a way to recreate them? Or am I screwed?
Is there a way to even preserve the data from the other shards of the same
index that did not encounter the issue?

-- Kris.

--
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/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

That's what I thought. Unfortunately, I did minimal replication and the
other copy was wiped out due to disk failure. Is there a way to run that
index without the bad shard (4 out of 5 still good)? I'm gonna guess no.

Thanks,
Kris.

On Thu, Mar 5, 2015 at 11:23 AM, Michael McCandless mike@elasticsearch.com
wrote:

That one shard is likely hosed.

But if you a good replica of that shard then you may be able to delete the
hosed shard and let ES recover from the good one.

Or restore from snapshot...

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:13 PM, krispyjala krispyjala@gmail.com wrote:

Hey all,
I ran exactly into this issue
Internal: Indexes unuseable after upgrade from 0.2 to 1.3 and cluster restart · Issue #7430 · elastic/elasticsearch · GitHub, probably
because some time back, we upgraded from 0.20.5 directly to 1.2.2. My
question is, so now one of my indices (just one shard really) is missing
the SegmentInfo file. Is there a way to recreate them? Or am I screwed?
Is there a way to even preserve the data from the other shards of the same
index that did not encounter the issue?

-- Kris.

--
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/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/8hCYXaWQLSk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu_gL7XY_oYRqrs0jYR5vXjSR9TZ18V%3D03m_bb%3DYbYQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

4

I'm not certain; maybe someone else can chime in if there's a way to
intentionally run in "degraded" mode where 1 out of 5 shards is missing?

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:30 PM, Kris Jirapinyo krispyjala@gmail.com wrote:

That's what I thought. Unfortunately, I did minimal replication and the
other copy was wiped out due to disk failure. Is there a way to run that
index without the bad shard (4 out of 5 still good)? I'm gonna guess no.

Thanks,
Kris.

On Thu, Mar 5, 2015 at 11:23 AM, Michael McCandless <
mike@elasticsearch.com> wrote:

That one shard is likely hosed.

But if you a good replica of that shard then you may be able to delete
the hosed shard and let ES recover from the good one.

Or restore from snapshot...

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:13 PM, krispyjala krispyjala@gmail.com wrote:

Hey all,
I ran exactly into this issue
Internal: Indexes unuseable after upgrade from 0.2 to 1.3 and cluster restart · Issue #7430 · elastic/elasticsearch · GitHub, probably
because some time back, we upgraded from 0.20.5 directly to 1.2.2. My
question is, so now one of my indices (just one shard really) is missing
the SegmentInfo file. Is there a way to recreate them? Or am I screwed?
Is there a way to even preserve the data from the other shards of the same
index that did not encounter the issue?

-- Kris.

--
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/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/8hCYXaWQLSk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu_gL7XY_oYRqrs0jYR5vXjSR9TZ18V%3D03m_bb%3DYbYQA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu_gL7XY_oYRqrs0jYR5vXjSR9TZ18V%3D03m_bb%3DYbYQA%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRfgQCPW0Yj%3DFxCS%3D2UoX8xnTTMEUAAFxD4UTmm9k%2B_6Cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

5

You can delete the shard file(s) and then it'll create an empty one to
replace it. Obviously, that means data loss.

On 6 March 2015 at 06:49, Michael McCandless mike@elasticsearch.com wrote:

I'm not certain; maybe someone else can chime in if there's a way to
intentionally run in "degraded" mode where 1 out of 5 shards is missing?

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:30 PM, Kris Jirapinyo krispyjala@gmail.com
wrote:

That's what I thought. Unfortunately, I did minimal replication and the
other copy was wiped out due to disk failure. Is there a way to run that
index without the bad shard (4 out of 5 still good)? I'm gonna guess no.

Thanks,
Kris.

On Thu, Mar 5, 2015 at 11:23 AM, Michael McCandless <
mike@elasticsearch.com> wrote:

That one shard is likely hosed.

But if you a good replica of that shard then you may be able to delete
the hosed shard and let ES recover from the good one.

Or restore from snapshot...

Mike McCandless

http://blog.mikemccandless.com

On Thu, Mar 5, 2015 at 2:13 PM, krispyjala krispyjala@gmail.com wrote:

Hey all,
I ran exactly into this issue
Internal: Indexes unuseable after upgrade from 0.2 to 1.3 and cluster restart · Issue #7430 · elastic/elasticsearch · GitHub, probably
because some time back, we upgraded from 0.20.5 directly to 1.2.2. My
question is, so now one of my indices (just one shard really) is missing
the SegmentInfo file. Is there a way to recreate them? Or am I screwed?
Is there a way to even preserve the data from the other shards of the same
index that did not encounter the issue?

-- Kris.

--
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/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/8hCYXaWQLSk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu_gL7XY_oYRqrs0jYR5vXjSR9TZ18V%3D03m_bb%3DYbYQA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu_gL7XY_oYRqrs0jYR5vXjSR9TZ18V%3D03m_bb%3DYbYQA%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAD7smRfgQCPW0Yj%3DFxCS%3D2UoX8xnTTMEUAAFxD4UTmm9k%2B_6Cg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAD7smRfgQCPW0Yj%3DFxCS%3D2UoX8xnTTMEUAAFxD4UTmm9k%2B_6Cg%40mail.gmail.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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_N%3DSKo1KWt6YGqhCNm6Wg79HEDTdK29Yc6bQWFc822Sg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.