-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-16423. S3Guard fsck: Check metadata consistency between S3 and metadatastore (log) #1208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
931137c
added integration tests for violation pairs. minor refactor
3cfd2c9
added AUTHORITATIVE_DIRECTORY_CONTENT_MISMATCH with test, removed ver…
4016351
factored out the big switch block from S3GuardFsckViolationHandler. U…
debe4c3
teardown added to itest
6565328
CLI test is working in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardT…
7d32a40
Remove ITestS3GuardDraftingFsck - move to a gist
fe0f7c4
fix findbugs and checkstyle issues. long line lenght checks are skipp…
60a25d3
some more comments
398c5d8
fix treewalk, add some tests, address Steve's comments. Tested in CLI…
61bbe4f
fix wrong missing versionid handling
7f904bf
check etag only for files, and not directories
d4e0c73
fixed based on comments part1 - there will be another part soon
6378165
ITestS3GuardFsck refactor
a9e9eb4
MOD_TIME_MISMATCH allowed within range
633d6cd
added TOMBSTONED_IN_MS_NOT_DELETED_IN_S3, fixed some checkstyle issues
1dfc3a1
fixed test failures
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now this is done on a per path basis is this probe adequate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is used in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardFsck#testIAuthoritativeDirectoryContentMismatch and I think that's the easiest to check in runtime. But I can use something else like getting it from the fs's config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If someone has configured the test path to be authoritative, then even if the store says non-auth you'll get auth-store-behaviours. Best to either unset the per-bucket/global auth mode settings in test config creation or check the auth mode of the actual test path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we're only using this for tests, so I'm not as worried as I was. +1 for this change