shard not fail after corrupted in update_by_id

[conicL]

When using the update API,

POST  index_name/_update/3625054589

I encountered a persistent failure with the specific exception:

{
  "error" : {
    "root_cause" : [
      {
        "type" : "exception",
        "reason" : "Failed to get type [_doc] and id [3625054589]"
      }
    ],
    "type" : "exception",
    "reason" : "Failed to get type [_doc] and id [3625054589]",
    "caused_by" : {
      "type" : "corrupt_index_exception",
      "reason" : "Corrupted: docID=418443, docBase=4, chunkDocs=31, numDocs=6350815 (resource=NIOFSIndexInput(path=\"es/data/nodes/0/indices/wxIwA-bDSouiwKS-4y1eiA/16/index/_p7lp9.fdt\"))"
    }
  },
  "status" : 500
}

I found that when retrieving the document in ShardGetService, the CorruptIndexException is not handled, so the shard fail is not triggered. My ES version is 7142, and the related code is

https://github.com/elastic/elasticsearch/blob/7.14/server/src/main/java/org/elasticsearch/index/get/ShardGetService.java#L222

If failShard is not executed, the exception will continue to occur, even if the current replica data might be correct. Therefore, should CorruptedIndexException be handled separately at this point?

[DaveCTurner]

Thank you very much for your interest in Elasticsearch. Unfortunately the issue you have reported relates to Elasticsearch version 7.14 which is very old and has passed end-of-life. We will not investigate issues related to unsupported versions here on Github, so I am closing this to indicate that no action is needed from the Elasticsearch development team. It's possible that you will find a volunteer to help you with this issue on the community forums, but our strong recommendation would be to upgrade to a supported version of Elasticsearch as a matter of some urgency. If you can reproduce your issue on a supported version then please open a fresh bug report.

Quoting the bug report form:

Please also check your OS is supported, and that the version of Elasticsearch has not passed end-of-life. If you are using an unsupported OS or an unsupported version then the issue is likely to be closed.

[conicL]

@DaveCTurner Yes, indeed 7.14 is a rather old version. I tried it on the latest version and found that the issue still exists. I have created a new issue #130076. I would appreciate it if you could kindly take another look.