完整磁盘后Elasticsearch无法正常工作

时间:2015-02-16 11:42:33

标签: elasticsearch

我腾出空间,重新启动服务(没有好处),然后重新启动但我仍然在elasticsearch.log中得到这个:

[2015-02-16 13:35:19,625][WARN ][cluster.action.shard     ] [Server] [logstash-2015.02.16][1] sending failed shard for [logstash-2015.02.16][1], node[PFamB-ZJS7CwSdyyAcP_8A], [P], s[INITIALIZING], indexUUID [tZ3I9HZ6TDaZSicIuGWRWQ], 
    reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[logstash-2015.02.16][1] 
    failed to recover shard]; nested: TranslogCorruptedException[translog corruption while reading from stream]; nested: ElasticsearchIllegalArgumentException[No version type match [83]]; ]]
[2015-02-16 13:35:19,625][WARN ][cluster.action.shard     ] [Server] [logstash-2015.02.16][1] received shard failed for [logstash-2015.02.16][1], node[PFamB-ZJS7CwSdyyAcP_8A], [P], s[INITIALIZING], indexUUID [tZ3I9HZ6TDaZSicIuGWRWQ], 
    reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[logstash-2015.02.16][1] 
    failed to recover shard]; nested: TranslogCorruptedException[translog corruption while reading from stream]; nested: ElasticsearchIllegalArgumentException[No version type match [83]]; ]]
[2015-02-16 13:35:43,570][DEBUG][action.index             ] [Server] observer: timeout notification from cluster service. timeout setting [1m], time since start [1m]
[2015-02-16 13:36:10,757][DEBUG][action.index             ] [Server] observer: timeout notification from cluster service. timeout setting [1m], time since start [1m]

我该怎么办?

2 个答案:

答案 0 :(得分:6)

Bigfoot的解决方案是唯一似乎有用的解决方案。

观察到的堆栈跟踪似乎与:https://github.com/elastic/elasticsearch/issues/12055

类似

此拉取请求应该可以解决问题:https://github.com/elastic/elasticsearch/pull/9797

但是升级到v1.5.0也会这样做。

因此唯一可行的方法是:

    private void button1_Click(object sender, EventArgs e)

    {
        string x;
        x = textBox1.Text;
        if (x != "")
        {
            some code...
        }
        else
        {
            MessageBox.Show("Please type something");
        }

删除所有正在恢复的文件。 当然这有副作用。

答案 1 :(得分:0)

我也遇到了同样的问题,日志中出现“No version type match”错误。

(另外,磁盘已满)

尝试使用bigfoot的解决方案来手动删除恢复文件,但它确实有效。

但这可能会产生一些负面影响。