似乎无法重新启动没有红色状态的弹性搜索 [英] Cannot seem to restart Elastic Search without red status

问题描述

每当我重新启动我唯一的弹性搜索节点，我只会得到红色状态，不得不删除我的数据目录，并丢失所有的数据...

whenever I restart my one and only Elastic Search node I keep just getting the red status and having to delete my data directory and lose all my data...

以下是重新启动节点的日志：

Here is the log from a restart of the node:

[2013-12-22 12:44:24,257][INFO ][node                     ] [Dominic Fortune] version[0.90.8], pid[1494], build[909b037/2013-12-18T16:08:16Z]
[2013-12-22 12:44:24,257][INFO ][node                     ] [Dominic Fortune] initializing ...
[2013-12-22 12:44:24,265][INFO ][plugins                  ] [Dominic Fortune] loaded [], sites [HQ, head]
[2013-12-22 12:44:26,818][INFO ][node                     ] [Dominic Fortune] initialized
[2013-12-22 12:44:26,818][INFO ][node                     ] [Dominic Fortune] starting ...
[2013-12-22 12:44:26,891][INFO ][transport                ] [Dominic Fortune] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/192.168.183.128:9300]}
[2013-12-22 12:44:29,919][INFO ][cluster.service          ] [Dominic Fortune] new_master [Dominic Fortune][5ddMpkRQTZa3TqQ-ljUabg][inet[/192.168.183.128:9300]], reason: zen-disco-join (elected_as_master)
[2013-12-22 12:44:29,951][INFO ][discovery                ] [Dominic Fortune] elasticsearch/5ddMpkRQTZa3TqQ-ljUabg
[2013-12-22 12:44:29,979][INFO ][http                     ] [Dominic Fortune] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/192.168.183.128:9200]}
[2013-12-22 12:44:29,980][INFO ][node                     ] [Dominic Fortune] started
[2013-12-22 12:44:29,987][INFO ][gateway                  ] [Dominic Fortune] recovered [0] indices into cluster_state
[2013-12-22 12:45:07,323][INFO ][cluster.metadata         ] [Dominic Fortune] [main] creating index, cause [api], shards [5]/[2], mappings []
[2013-12-22 12:45:17,669][INFO ][cluster.metadata         ] [Dominic Fortune] [main] create_mapping [_default_]
[2013-12-22 12:45:17,680][INFO ][cluster.metadata         ] [Dominic Fortune] [main] create_mapping [help]
[2013-12-22 12:47:19,818][INFO ][node                     ] [Dominic Fortune] stopping ...
[2013-12-22 12:47:19,845][INFO ][node                     ] [Dominic Fortune] stopped
[2013-12-22 12:47:19,845][INFO ][node                     ] [Dominic Fortune] closing ...
[2013-12-22 12:47:19,856][INFO ][node                     ] [Dominic Fortune] closed
[2013-12-22 12:47:45,495][INFO ][node                     ] [Stryker, William] version[0.90.8], pid[1695], build[909b037/2013-12-18T16:08:16Z]
[2013-12-22 12:47:45,496][INFO ][node                     ] [Stryker, William] initializing ...
[2013-12-22 12:47:45,502][INFO ][plugins                  ] [Stryker, William] loaded [], sites [HQ, head]
[2013-12-22 12:47:48,068][INFO ][node                     ] [Stryker, William] initialized
[2013-12-22 12:47:48,068][INFO ][node                     ] [Stryker, William] starting ...
[2013-12-22 12:47:48,140][INFO ][transport                ] [Stryker, William] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/192.168.183.128:9300]}
[2013-12-22 12:47:51,170][INFO ][cluster.service          ] [Stryker, William] new_master [Stryker, William][rMklMXasRDS4lURA0wQ7lQ][inet[/192.168.183.128:9300]], reason: zen-disco-join (elected_as_master)
[2013-12-22 12:47:51,198][INFO ][discovery                ] [Stryker, William] elasticsearch/rMklMXasRDS4lURA0wQ7lQ
[2013-12-22 12:47:51,222][INFO ][http                     ] [Stryker, William] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/192.168.183.128:9200]}
[2013-12-22 12:47:51,223][INFO ][node                     ] [Stryker, William] started
[2013-12-22 12:47:51,242][INFO ][gateway                  ] [Stryker, William] recovered [1] indices into cluster_state

As你可以看到 Dominic Fortune downs然后 Stryker，William 联机。没有其他节点，我的集群上HQ插件的状态表示1个节点。

As you can see Dominic Fortune downs and then Stryker, William comes online after the node restart. There are no other nodes, the status on my cluster from the HQ plugin says 1 node.

尽管如此，我无法阻止我的集群进入红色状态

Despite this I cannot stop my cluster from going into red status whenever I do this.

如何解决我看不到的问题？

How can I fix a problem I cannot see?

推荐答案

确实，我实际上已经能够尝试和错误修复。

Ok I actually have been able to trial and error a fix.

问题是当我重新启动节点时索引中没有数据。

The problem is that there was no data in the indexes when I restarted the node.

由于一些奇怪的原因，这使得弹性搜索爆炸，好像它找不到所有的文件，实际上没有找到文件。

For some odd reason this makes Elastic Search explode as though it cannot find all the documents when in fact there are no documents to be found.

在Google Group上发布后，我发现这是我的愚蠢，因为我使用2的副本设置，法定人数期待多于一个节点线上。

After posting on the Google Group I found this to be my stupidity, since I used a replica setting of 2 the quorum was expecting more than one node online.

当没有因数据不足等原因时，它将失败，并且不能恢复要在弹性搜索重新启动时使用的索引。

When there wasn't due to lack of data etc it would fail and not recover the index to be used on the restart of Elastic Search.

Dumbo me。

这篇关于似乎无法重新启动没有红色状态的弹性搜索的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！