From 8949cb85fbac3e2209b5ca05936c8e2d009809c2 Mon Sep 17 00:00:00 2001
From: Simon Willnauer <simonw@apache.org>
Date: Tue, 19 May 2015 22:24:02 +0200
Subject: [PATCH] [RECOVERY] Add engine failure on recovery finalization
 corruption back

This engine failure on finalization corruption was lost on refactorings and
should be added back.
---
 .../elasticsearch/indices/recovery/RecoverySourceHandler.java    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java b/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
index b131f11fbc0..2e2497fe7cb 100644
--- a/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
+++ b/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
@@ -420,6 +420,7 @@ public class RecoverySourceHandler {
                                     for (StoreFileMetaData md : metadata) {
                                         logger.debug("{} checking integrity for file {} after remove corruption exception", shard.shardId(), md);
                                         if (store.checkIntegrityNoException(md) == false) { // we are corrupted on the primary -- fail!
+                                            shard.engine().failEngine("recovery", corruptIndexException);
                                             logger.warn("{} Corrupted file detected {} checksum mismatch", shard.shardId(), md);
                                             throw corruptIndexException;
                                         }