Unexpected error during recovery but recovery id recoveryId is finished – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch encounters an unexpected issue during the recovery process of a shard, but the recovery process has already been marked as finished. This could be due to a network glitch, disk I/O issue, or a bug in Elasticsearch. To resolve this issue, you can try the following: 1) Check the Elasticsearch logs for more detailed error messages. 2) Ensure the health of your network and disk I/O. 3) Upgrade Elasticsearch to the latest stable version to rule out any bugs. 4) If the error persists, consider reindexing your data.

This guide will help you check for common problems that cause the log ” unexpected error during recovery; but recovery id [” + recoveryId + “] is finished ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, recovery.

Log Context

Log “unexpected error during recovery; but recovery id [” + recoveryId + “] is finished” classname is PeerRecoveryTargetService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        new RecoveryFailedException(recoveryRef.target().state(); "unexpected error"; e);
                        true // be safe
                } else {
                    logger.debug(() -> "unexpected error during recovery; but recovery id [" + recoveryId + "] is finished"; e);



How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?