# Missing SegmentInfo files after upgrade question (Issue 7430) **URL:** \ **Category:** Elasticsearch\ **Created:** [March 5, 2015, 7:13pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535 "2015-03-05T19:13:08Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![krispyjala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krispyjala/32/846_2.png) [@krispyjala](https://discuss.elastic.co/u/krispyjala)\ **Post date:** [March 5, 2015, 7:13pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/1 "2015-03-05T19:13:08Z")
Hey all, I ran exactly into this issue [https://github.com/elasticsearch/elasticsearch/issues/7430](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](mailto: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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\ **Post date:** [March 5, 2015, 7:23pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/2 "2015-03-05T19:23:37Z")
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](http://blog.mikemccandless.com) On Thu, Mar 5, 2015 at 2:13 PM, krispyjala [krispyjala@gmail.com](mailto: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](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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![krispyjala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krispyjala/32/846_2.png) [@krispyjala](https://discuss.elastic.co/u/krispyjala)\ **Post date:** [March 5, 2015, 7:30pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/3 "2015-03-05T19:30:55Z")
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](mailto: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](http://blog.mikemccandless.com) > > On Thu, Mar 5, 2015 at 2:13 PM, krispyjala [krispyjala@gmail.com](mailto: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](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](mailto: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) > > [https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\ **Post date:** [March 5, 2015, 7:49pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/4 "2015-03-05T19:49:58Z")
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](http://blog.mikemccandless.com) On Thu, Mar 5, 2015 at 2:30 PM, Kris Jirapinyo [krispyjala@gmail.com](mailto: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](mailto: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](http://blog.mikemccandless.com) > > > > On Thu, Mar 5, 2015 at 2:13 PM, krispyjala [krispyjala@gmail.com](mailto: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](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](mailto: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) > > > [https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](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](mailto: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) > > [https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu\_gL7XY\_oYRqrs0jYR5vXjSR9TZ18V%3D03m\_bb%3DYbYQA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 5, 2015, 10:00pm UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/5 "2015-03-05T22:00:31Z")
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](mailto: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](http://blog.mikemccandless.com) > > On Thu, Mar 5, 2015 at 2:30 PM, Kris Jirapinyo [krispyjala@gmail.com](mailto: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](mailto: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](http://blog.mikemccandless.com) > > > > > > On Thu, Mar 5, 2015 at 2:13 PM, krispyjala [krispyjala@gmail.com](mailto: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](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](mailto: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) > > > > [https://groups.google.com/d/msgid/elasticsearch/979ff875-792e-4ccc-b21c-fcdfa49fa2d6%40googlegroups.com?utm\_medium=email&utm\_source=footer](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](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](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](mailto: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) > > > [https://groups.google.com/d/msgid/elasticsearch/CAD7smRce2tOnYkfEUkkTShYS1SwxTRErepMjUFdSeOe%3DF5-69Q%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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) > > [https://groups.google.com/d/msgid/elasticsearch/CAKq8e-nu\_gL7XY\_oYRqrs0jYR5vXjSR9TZ18V%3D03m\_bb%3DYbYQA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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) > [https://groups.google.com/d/msgid/elasticsearch/CAD7smRfgQCPW0Yj%3DFxCS%3D2UoX8xnTTMEUAAFxD4UTmm9k%2B\_6Cg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](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](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](mailto: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](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_N%3DSKo1KWt6YGqhCNm6Wg79HEDTdK29Yc6bQWFc822Sg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:28am UTC](https://discuss.elastic.co/t/missing-segmentinfo-files-after-upgrade-question-issue-7430/22535/6 "2017-07-06T00:28:14Z")