Mention IndexFormatToo{Old,New}Exception as corruption
#104204
Merged
+8
−2
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
If a file header is corrupted then the exception may be reported as a bad index format version rather than a checksum mismatch. This commit adjusts the docs to cover this case.
DaveCTurner
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
Team:Distributed (Obsolete)
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
| @@ -50,8 +57,7 @@ system previously confirmed to {es} that this file was durably synced to disk. | |||
| On Linux this means that the `fsync()` system call returned successfully. {es} | |||
| sometimes reports that an index is corrupt because a file needed for recovery | |||
| is missing, or it exists but has been truncated or is missing its footer. This | |||
| indicates that your storage system acknowledges durable writes incorrectly or | |||
| that some external process has modified the data {es} previously wrote to disk. | |||
| may indicate that your storage system acknowledges durable writes incorrectly. | |||
There was a problem hiding this comment.
I do not think this change is related to the title. Was it intentional?
There was a problem hiding this comment.
Yeah it was intentional, I meant to fix this in the last change to this file but missed it.
There was a problem hiding this comment.
Why would you like to remove the mention of another process? My understanding is that it is still a possibility. Is it mentioned anywhere else?
idegtiarenko
approved these changes
Jan 10, 2024
DaveCTurner
added
the
auto-merge-without-approval
DaveCTurner
deleted the
2024/01/10/IndexFormatTooOldException-corruption
branch
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 10, 2024
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 10, 2024
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 10, 2024
…104207) If a file header is corrupted then the exception may be reported as a bad index format version rather than a checksum mismatch. This commit adjusts the docs to cover this case.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 10, 2024
…104208) If a file header is corrupted then the exception may be reported as a bad index format version rather than a checksum mismatch. This commit adjusts the docs to cover this case.
DaveCTurner
restored the
2024/01/10/IndexFormatTooOldException-corruption
branch
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.
If a file header is corrupted then the exception may be reported as a
bad index format version rather than a checksum mismatch. This commit
adjusts the docs to cover this case.