Copy checkpoint atomically when rolling generation #35407
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Today when rolling a transog generation we copy the checkpoint from `translog.ckp` to `translog-nnnn.ckp` using a simple `Files.copy()` followed by appropriate `fsync()` calls. The copy operation is not atomic, so if we crash at the wrong moment we can leave an incomplete checkpoint file on disk. In practice the checkpoint is so small that it's either empty or fully written. However, we do not correctly handle the case where it's empty when the node restarts. In contrast, in `recoverFromFiles()` we _do_ copy the checkpoint atomically. This commit extracts the atomic copy operation from `recoverFromFiles()` and re-uses it in `rollGeneration()`.
DaveCTurner
added
>bug
v7.0.0
:Distributed Indexing/Engine
|
Pinging @elastic/es-distributed |
|
This situation occurred in https://discuss.elastic.co/t/failed-shard-after-ooming-corrupt-index/155612/3. I recognise there's no tests for this change yet, because I don't know a good way to simulate this situation. Any ideas? |
|
God I don’t know how often I looked at this code and I missed that?! Code LGTM, regarding testing I think we can add a randomly throwing FS impl that’s corrupting files if they are not fsynced. We do this in some lucene testing directories but that’s a bigger change. I am ok with getting this in as is and start the conversation on a follow up issue |
bleskes
approved these changes
Nov 9, 2018
s1monw
approved these changes
Nov 9, 2018
DaveCTurner
added a commit
that referenced
this pull request
Nov 23, 2018
Today when rolling a transog generation we copy the checkpoint from `translog.ckp` to `translog-nnnn.ckp` using a simple `Files.copy()` followed by appropriate `fsync()` calls. The copy operation is not atomic, so if we crash at the wrong moment we can leave an incomplete checkpoint file on disk. In practice the checkpoint is so small that it's either empty or fully written. However, we do not correctly handle the case where it's empty when the node restarts. In contrast, in `recoverFromFiles()` we _do_ copy the checkpoint atomically. This commit extracts the atomic copy operation from `recoverFromFiles()` and re-uses it in `rollGeneration()`.
original-brownbear
pushed a commit
that referenced
this pull request
Nov 23, 2018
Today when rolling a transog generation we copy the checkpoint from `translog.ckp` to `translog-nnnn.ckp` using a simple `Files.copy()` followed by appropriate `fsync()` calls. The copy operation is not atomic, so if we crash at the wrong moment we can leave an incomplete checkpoint file on disk. In practice the checkpoint is so small that it's either empty or fully written. However, we do not correctly handle the case where it's empty when the node restarts. In contrast, in `recoverFromFiles()` we _do_ copy the checkpoint atomically. This commit extracts the atomic copy operation from `recoverFromFiles()` and re-uses it in `rollGeneration()`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today when rolling a transog generation we copy the checkpoint from
translog.ckptotranslog-nnnn.ckpusing a simpleFiles.copy()followed byappropriate
fsync()calls. The copy operation is not atomic, so if we crashat the wrong moment we can leave an incomplete checkpoint file on disk. In
practice the checkpoint is so small that it's either empty or fully written.
However, we do not correctly handle the case where it's empty when the node
restarts.
In contrast, in
recoverFromFiles()we do copy the checkpoint atomically.This commit extracts the atomic copy operation from
recoverFromFiles()andre-uses it in
rollGeneration().