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
This commit is contained in:
parent
33faf5ec70
commit
e3b0cc9867
|
@ -246,9 +246,6 @@ public class RecoverySourceHandler {
|
||||||
}
|
}
|
||||||
return tracker.getCheckpoint() >= endingSeqNo;
|
return tracker.getCheckpoint() >= endingSeqNo;
|
||||||
} else {
|
} 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;
|
return false;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue