Oh I forgot to mention... I am using Elasticsearch version 1.0.1
Thanks!
On Saturday, March 1, 2014 9:42:04 PM UTC-8, hrishikesh prabhune wrote:
Hello all,
I have an elasticsearch cluster of 16 nodes , all of which are eligible
master and data nodes. I had to add some load balancing nodes to the
cluster so i added 6 extra nodes to the cluster . These newly added nodes
are all eligible master nodes only(not eligible data nodes). I restarted
the whole cluster by making the original 16 nodes to be eligible data nodes
only and the newly added 6 nodes were kept as eligible master nodes only.
During the first restart after changing the whole configuration of cluster
I started getting these INFO messages in the logs :
[2014-03-02 04:33:57,857][INFO ][gateway.local.state.meta ] [node1] [%user
%index] dangling index, exists on local file system, but not in cluster
metadata, scheduling to delete in [2h], auto import to cluster state [YES]
I thought the indices were about to be deleted so I immediately shutdown
the cluster and reverted back to the original configuration.
Can anyone shed a light on these info messages? According to my
understanding, only the cluster meta data of theses indices were about to
changed or deleted but not the data in the index. It would be great if
anyone could give a quick explanation about why I am getting these messages.
Thanks in advance!!
On Saturday, March 1, 2014 9:42:04 PM UTC-8, hrishikesh prabhune wrote:
Hello all,
I have an elasticsearch cluster of 16 nodes , all of which are eligible
master and data nodes. I had to add some load balancing nodes to the
cluster so i added 6 extra nodes to the cluster . These newly added nodes
are all eligible master nodes only(not eligible data nodes). I restarted
the whole cluster by making the original 16 nodes to be eligible data nodes
only and the newly added 6 nodes were kept as eligible master nodes only.
During the first restart after changing the whole configuration of cluster
I started getting these INFO messages in the logs :
[2014-03-02 04:33:57,857][INFO ][gateway.local.state.meta ] [node1] [%user
%index] dangling index, exists on local file system, but not in cluster
metadata, scheduling to delete in [2h], auto import to cluster state [YES]
I thought the indices were about to be deleted so I immediately shutdown
the cluster and reverted back to the original configuration.
Can anyone shed a light on these info messages? According to my
understanding, only the cluster meta data of theses indices were about to
changed or deleted but not the data in the index. It would be great if
anyone could give a quick explanation about why I am getting these messages.
Thanks in advance!!
On Saturday, March 1, 2014 9:42:04 PM UTC-8, hrishikesh prabhune wrote:
Hello all,
I have an elasticsearch cluster of 16 nodes , all of which are eligible
master and data nodes. I had to add some load balancing nodes to the
cluster so i added 6 extra nodes to the cluster . These newly added nodes
are all eligible master nodes only(not eligible data nodes). I restarted
the whole cluster by making the original 16 nodes to be eligible data nodes
only and the newly added 6 nodes were kept as eligible master nodes only.
During the first restart after changing the whole configuration of cluster
I started getting these INFO messages in the logs :
[2014-03-02 04:33:57,857][INFO ][gateway.local.state.meta ] [node1] [%user
%index] dangling index, exists on local file system, but not in cluster
metadata, scheduling to delete in [2h], auto import to cluster state [YES]
I thought the indices were about to be deleted so I immediately shutdown
the cluster and reverted back to the original configuration.
Can anyone shed a light on these info messages? According to my
understanding, only the cluster meta data of theses indices were about to
changed or deleted but not the data in the index. It would be great if
anyone could give a quick explanation about why I am getting these messages.
Thanks in advance!!
On Saturday, March 1, 2014 9:42:04 PM UTC-8, hrishikesh prabhune wrote:
Hello all,
I have an elasticsearch cluster of 16 nodes , all of which are eligible
master and data nodes. I had to add some load balancing nodes to the
cluster so i added 6 extra nodes to the cluster . These newly added nodes
are all eligible master nodes only(not eligible data nodes). I restarted
the whole cluster by making the original 16 nodes to be eligible data nodes
only and the newly added 6 nodes were kept as eligible master nodes only.
During the first restart after changing the whole configuration of cluster
I started getting these INFO messages in the logs :
[2014-03-02 04:33:57,857][INFO ][gateway.local.state.meta ] [node1] [%user
%index] dangling index, exists on local file system, but not in cluster
metadata, scheduling to delete in [2h], auto import to cluster state [YES]
I thought the indices were about to be deleted so I immediately shutdown
the cluster and reverted back to the original configuration.
Can anyone shed a light on these info messages? According to my
understanding, only the cluster meta data of theses indices were about to
changed or deleted but not the data in the index. It would be great if
anyone could give a quick explanation about why I am getting these messages.
Thanks in advance!!
--
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/74ace4dd-b77d-48ea-8622-033f903e2e51%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.