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

big*_*oot 8 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]
Run Code Online (Sandbox Code Playgroud)

我该怎么办?

小智 6

Bigfoot的解决方案是唯一可行的解​​决方案.

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

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

但也升级到V1.5.0并没有做的伎俩.

因此唯一有效的方法:

find  /var/lib/elasticsearch/elasticsearch/nodes/ -name "*.recovering"
Run Code Online (Sandbox Code Playgroud)

并删除所有恢复的文件.当然这有副作用.


Bri*_*edt 0

我也遇到了同样的问题,日志中出现“无版本类型匹配”错误。

(此外,磁盘已满后)

尝试了大脚的解决方案来手动删除恢复文件并且它有效。

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