修复 Elasticsearch 中损坏的索引

最新推荐文章于 2025-11-10 02:58:10 发布

原创

最新推荐文章于 2025-11-10 02:58:10 发布 · 2.7k 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#elasticsearch #java

本文介绍了在生产环境中遇到Elasticsearch因Force Merge API导致的红色索引问题，详细解析了分析和修复过程。尝试了Thiago Souza和Yannick Welsch的解决方案，最终通过Lucene的CheckIndex工具移除损坏标记文件实现恢复，避免了数据丢失。

原文发布于：https://mincong.io/cn/elasticsearch-corrupted-index/

问题

在生产线上因为使用 Force Merge API 出现了红色索引：

"store_exception": {
   
   
    "type": "corrupt_index_exception",
    "reason": "failed engine (reason: [corrupt file (source: [force merge])]) (resource=preexisting_corruption)",
        "caused_by": {
   
   
        "type": "i_o_exception",
        "reason": "failed engine (reason: [corrupt file (source: [force merge])])",
        "caused_by": {
   
   
            "type": "corrupt_index_exception",
            "reason": "checksum failed (hardware problem?) : expected=70193aa8 actual=c48ab092 (resource=BufferedChecksumIndexInput(NIOFSIndexInput(path=\"/usr/share/elasticsearch/data/nodes/0/indices/w76sdoDFRm-xxxxxxxxxxx/0/index/_ke.fdt\")))"
        }
    }
}