Failed to load metata when restarting elasticsearch

Now I have found the corrupted file $(path.data)/nodes/0/_state/_10up.fdt with the command below.

grep 'sql_illegal_argument_exception' -r $(path.data)/nodes/0

In my view, It's this file that stop the elasticsearch node to be start. After read the PR #72274 conversation, I got some of why the issue happened, although not clear about the detail. It seems because of the bug #72274 fixed, the response json "{"root_cause": [{"type": "sql_illegal_argument_exception.." which should only be sent as a query response was writed to the file $(path.data)/nodes/0/_state/_10up.fdt by mistake. Then it failed to started when we restart elasticsearch node, because the elasticsearch can't not parse the file $(path.data)/nodes/0/_state/_10up.fdt correctly as the error message says below.

Caused by: com.fasterxml.jackson.core.JsonParseException: Input does not start with Smile format header (first byte = 0x7b) -- rather, it starts with '{' (plain JSON input?) -- can not parse
at [Source: (byte)"error": {"root_cause": [{"type": "sql_illegal_argument_exception", "reason": "The default limit [65535] for aggerate sorting has been reached; please specify a LIMIT"}], "type": }.... debugA2s?index.indexing.slowlog.threshold.index.infoA5s?index.indexing.slowlog.threshold.index.traceD500ms?index.......index.number_of_replicas"[truncated 1339 bytes]; line: -1, column: 0]