Closed Index missing after restarting the elasticsearch cluster

error804 · September 18, 2013, 10:09am

We are running elasticsearch in extra large instances of amazon ec2. After
restarting the cluster the closed index are not present in that cluster. So
we are seeking for some help, can anybody have some ideas about that.

Thanks

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Ivan · September 18, 2013, 3:21pm

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045
pawansharma2045@gmail.comwrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

error804 · September 19, 2013, 8:24am

Thanks for the reply.

No data doesn't exist. That index as well as data lost. We have to process
that data again.
You have got any ides about that.

Regards
Pawan

On Wed, Sep 18, 2013 at 9:06 PM, Ivan Brusic ivan@brusic.com wrote:

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045 <
pawansharma2045@gmail.com> wrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

spinscale · September 19, 2013, 8:36am

Hey,

can you create a reproducible example and provide some more information?
I'd like to see

how you create this index (any special configuration, also in your .yml
file)
how you close the index?
is there anything in your logfiles? any exceptions?
What elasticsearch version are you using?

Thanks!

--Alex

On Thu, Sep 19, 2013 at 10:24 AM, Pawan Sharma pawansharma2045@gmail.comwrote:

Thanks for the reply.

No data doesn't exist. That index as well as data lost. We have to process
that data again.
You have got any ides about that.

Regards
Pawan

On Wed, Sep 18, 2013 at 9:06 PM, Ivan Brusic ivan@brusic.com wrote:

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045 <
pawansharma2045@gmail.com> wrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

error804 · September 19, 2013, 9:19am

Hi,

We use python script to copy index from transient cluster.

This is used to creat index while copying from transient. Here we give source
index [FROM] and destination Index [To Be copied] .
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index+'/
-d @' + mapping_path + 'mapping', shell=True)

and

For Closing indexes we call

call('curl -XPOST ' + source_instances[0] + ':9200/' + source_index
+'/_close', shell=True)
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index
+'/_close', shell=True)

There is nothing abnormal or any logs or exceptions . Currently we are
using 0.90.3

and nothing special configuration in .yml file.

Regards
Pawan

On Thu, Sep 19, 2013 at 2:21 PM, Alexander Reelsen alr@spinscale.de wrote:

Hey,

can you create a reproducible example and provide some more information?
I'd like to see

how you create this index (any special configuration, also in your .yml
file)

how you close the index?

is there anything in your logfiles? any exceptions?

What elasticsearch version are you using?

Thanks!

--Alex

On Thu, Sep 19, 2013 at 10:24 AM, Pawan Sharma pawansharma2045@gmail.comwrote:

Thanks for the reply.

No data doesn't exist. That index as well as data lost. We have to
process that data again.
You have got any ides about that.

Regards
Pawan

On Wed, Sep 18, 2013 at 9:06 PM, Ivan Brusic ivan@brusic.com wrote:

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045 <
pawansharma2045@gmail.com> wrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

Ivan · September 19, 2013, 6:32pm

Where there any open indices during the restart?

On Thu, Sep 19, 2013 at 2:19 AM, Pawan Sharma pawansharma2045@gmail.comwrote:

Hi,

We use python script to copy index from transient cluster.

This is used to creat index while copying from transient. Here we give source
index [FROM] and destination Index [To Be copied] .
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index+'/
-d @' + mapping_path + 'mapping', shell=True)

and

For Closing indexes we call

call('curl -XPOST ' + source_instances[0] + ':9200/' + source_index
+'/_close', shell=True)
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index
+'/_close', shell=True)

There is nothing abnormal or any logs or exceptions . Currently we are
using 0.90.3

and nothing special configuration in .yml file.

Regards
Pawan

On Thu, Sep 19, 2013 at 2:21 PM, Alexander Reelsen alr@spinscale.dewrote:

Hey,

can you create a reproducible example and provide some more information?
I'd like to see

how you create this index (any special configuration, also in your .yml
file)

how you close the index?

is there anything in your logfiles? any exceptions?

What elasticsearch version are you using?

Thanks!

--Alex

On Thu, Sep 19, 2013 at 10:24 AM, Pawan Sharma <pawansharma2045@gmail.com

wrote:

Thanks for the reply.

No data doesn't exist. That index as well as data lost. We have to
process that data again.
You have got any ides about that.

Regards
Pawan

On Wed, Sep 18, 2013 at 9:06 PM, Ivan Brusic ivan@brusic.com wrote:

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045 <
pawansharma2045@gmail.com> wrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
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.
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

error804 · September 20, 2013, 4:58am

HI ivan Brusic,

There are open about 30 open indices during the restart.But the problem is
only that the closed indices are missed.

Regards

On Fri, Sep 20, 2013 at 12:17 AM, Ivan Brusic ivan@brusic.com wrote:

Where there any open indices during the restart?

On Thu, Sep 19, 2013 at 2:19 AM, Pawan Sharma pawansharma2045@gmail.comwrote:

Hi,

We use python script to copy index from transient cluster.

This is used to creat index while copying from transient. Here we give source
index [FROM] and destination Index [To Be copied] .
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index+'/
-d @' + mapping_path + 'mapping', shell=True)

and

For Closing indexes we call

call('curl -XPOST ' + source_instances[0] + ':9200/' + source_index
+'/_close', shell=True)
call('curl -XPOST ' + destination_instances[0] + ':9200/' + dest_index
+'/_close', shell=True)

There is nothing abnormal or any logs or exceptions . Currently we are
using 0.90.3

and nothing special configuration in .yml file.

Regards
Pawan

On Thu, Sep 19, 2013 at 2:21 PM, Alexander Reelsen alr@spinscale.dewrote:

Hey,

can you create a reproducible example and provide some more information?
I'd like to see

how you create this index (any special configuration, also in your
.yml file)

how you close the index?

is there anything in your logfiles? any exceptions?

What elasticsearch version are you using?

Thanks!

--Alex

On Thu, Sep 19, 2013 at 10:24 AM, Pawan Sharma <
pawansharma2045@gmail.com> wrote:

Thanks for the reply.

No data doesn't exist. That index as well as data lost. We have to
process that data again.
You have got any ides about that.

Regards
Pawan

On Wed, Sep 18, 2013 at 9:06 PM, Ivan Brusic ivan@brusic.com wrote:

Does the data exist in the data directory (path.data)?

Cheers,

Ivan

On Wed, Sep 18, 2013 at 3:09 AM, pawansharma2045 <
pawansharma2045@gmail.com> wrote:

We are running elasticsearch in extra large instances of amazon ec2.
After restarting the cluster the closed index are not present in that
cluster. So we are seeking for some help, can anybody have some ideas about
that.

Thanks

--
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.
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.
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.
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.
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.

Topic		Replies	Views
Closed Index missing after restarting the elasticsearch cluster Elasticsearch	1	270	July 6, 2017
Hundreds of indices missing Elasticsearch	3	283	July 6, 2017
Missing closed indexes after adding node Elasticsearch	3	386	July 6, 2017
Deleted index shows up after cluster restart Elasticsearch	5	1190	July 6, 2017
/_stats endpoint not showing closed indices? Elasticsearch	3	496	July 6, 2017

Closed Index missing after restarting the elasticsearch cluster

For Closing indexes we call

For Closing indexes we call

For Closing indexes we call

Related topics