From e3b0cc986743197e895be2eb756797711a13d8de Mon Sep 17 00:00:00 2001
From: Jason Tedor <jason@tedor.me>
Date: Thu, 7 Sep 2017 21:57:08 -0400
Subject: [PATCH] Remove norelease regarding destroying history

This commit removes a norelease from the codebase now that there is a CI
job that fails on the norelease pattern being present. Instead, a new
issue has been opened to track this one.

Relates #26544
---
 .../elasticsearch/indices/recovery/RecoverySourceHandler.java  | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/core/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java b/core/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
index 28e2e8d32c8..73ab3197568 100644
--- a/core/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
+++ b/core/src/main/java/org/elasticsearch/indices/recovery/RecoverySourceHandler.java
@@ -246,9 +246,6 @@ public class RecoverySourceHandler {
             }
             return tracker.getCheckpoint() >= endingSeqNo;
         } else {
-            // norelease this can currently happen if a snapshot restore rolls the primary back to a previous commit point; in this
-            // situation the local checkpoint on the replica can be far in advance of the maximum sequence number on the primary violating
-            // all assumptions regarding local and global checkpoints
             return false;
         }
     }