You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use lastSyncedGlobalCheckpoint in deletion policy (#27826)
Today we use the in-memory global checkpoint from SequenceNumbersService
to clean up unneeded commit points, however the latest global checkpoint
may haven't fsynced to the disk yet. If the translog checkpoint fsync
failed and we already use a higher global checkpoint to clean up commit
points, then we may have removed a safe commit which we try to keep for
recovery.
This commit updates the deletion policy using lastSyncedGlobalCheckpoint
from Translog rather the in memory global checkpoint.
Relates #27606
// We expect that this shard already exists, so it must already have an existing translog else something is badly wrong!
447
447
if (translogUUID == null) {
448
448
thrownewIndexFormatTooOldException("translog", "translog has no generation nor a UUID - this might be an index from a previous version consider upgrading to N-1 first");
@@ -492,14 +492,13 @@ public long getWritingBytes() {
492
492
}
493
493
494
494
/**
495
-
* Reads the current stored translog ID from the IW commit data. If the id is not found, recommits the current
496
-
* translog id into lucene and returns null.
495
+
* Reads the current stored translog ID from the last commit data.
0 commit comments