Quick question, please. If a node re-joins the cluster after it got
rebooted a few minutes ago, will ES make use of the old shards on this node
under any circumstances? Are they ever going to be used? For example, if a
shard does not exist anywhere else other than an old copy on this node,
will it be used?
Yes, if the recovery of an index succeeds, the shards of the rejoined node
for the index will be used. Do you mean orphaned shards, where the index
does no longer exist?
Quick question, please. If a node re-joins the cluster after it got
rebooted a few minutes ago, will ES make use of the old shards on this node
under any circumstances? Are they ever going to be used? For example, if a
shard does not exist anywhere else other than an old copy on this node,
will it be used?
So upon rebooting of a node, I should NOT attempt to remove all the
existing ES data before re-joining the cluster because these data might be
useful?
Yes, I meant orphaned shards.
Thanks.
Yongtao
On Monday, June 23, 2014 12:02:53 PM UTC-7, Jörg Prante wrote:
Yes, if the recovery of an index succeeds, the shards of the rejoined node
for the index will be used. Do you mean orphaned shards, where the index
does no longer exist?
Jörg
On Mon, Jun 23, 2014 at 7:26 PM, Yongtao You <yongt...@gmail.com
<javascript:>> wrote:
Hi,
Quick question, please. If a node re-joins the cluster after it got
rebooted a few minutes ago, will ES make use of the old shards on this node
under any circumstances? Are they ever going to be used? For example, if a
shard does not exist anywhere else other than an old copy on this node,
will it be used?
No, you must not remove any data. There are several options what ES can do
with orphaned shards:
Example of a log entry when orphaned shard is detected:
[2014-06-23 21:46:05,841][INFO ][gateway.local.state.meta ] [Lonnie
Thompson Lincoln] [test] dangling index, exists on local file system, but
not in cluster metadata, scheduling to delete in [2h], auto import to
cluster state [YES]
You can test this very easily by starting two nodes, index two docs, stop
one node, delete the index, and start the stopped node again.
So upon rebooting of a node, I should NOT attempt to remove all the
existing ES data before re-joining the cluster because these data might be
useful?
Yes, I meant orphaned shards.
Thanks.
Yongtao
On Monday, June 23, 2014 12:02:53 PM UTC-7, Jörg Prante wrote:
Yes, if the recovery of an index succeeds, the shards of the rejoined
node for the index will be used. Do you mean orphaned shards, where the
index does no longer exist?
Quick question, please. If a node re-joins the cluster after it got
rebooted a few minutes ago, will ES make use of the old shards on this node
under any circumstances? Are they ever going to be used? For example, if a
shard does not exist anywhere else other than an old copy on this node,
will it be used?
Thanks.
Yongtao
--
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 elasticsearc...@googlegroups.com.
Example of a log entry when orphaned shard is detected:
[2014-06-23 21:46:05,841][INFO ][gateway.local.state.meta ] [Lonnie
Thompson Lincoln] [test] dangling index, exists on local file system, but
not in cluster metadata, scheduling to delete in [2h], auto import to
cluster state [YES]
You can test this very easily by starting two nodes, index two docs, stop
one node, delete the index, and start the stopped node again.
Jörg
On Mon, Jun 23, 2014 at 9:18 PM, Yongtao You <yongt...@gmail.com
<javascript:>> wrote:
So upon rebooting of a node, I should NOT attempt to remove all the
existing ES data before re-joining the cluster because these data might be
useful?
Yes, I meant orphaned shards.
Thanks.
Yongtao
On Monday, June 23, 2014 12:02:53 PM UTC-7, Jörg Prante wrote:
Yes, if the recovery of an index succeeds, the shards of the rejoined
node for the index will be used. Do you mean orphaned shards, where the
index does no longer exist?
Quick question, please. If a node re-joins the cluster after it got
rebooted a few minutes ago, will ES make use of the old shards on this node
under any circumstances? Are they ever going to be used? For example, if a
shard does not exist anywhere else other than an old copy on this node,
will it be used?
Thanks.
Yongtao
--
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 elasticsearc...@googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.