-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-16384: Avoid inconsistencies between DDB and S3 #1003
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
HADOOP-16384: Avoid inconsistencies between DDB and S3 #1003
Conversation
🎊 +1 overall
This message was automatically generated. |
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
76a1dde
to
8b2837a
Compare
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
Outdated
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
…ystem in a DDB table * Needs a -force argument, otherwise it's just a dry run * With tests * And coverage in the testing docs Change-Id: I9b0e5edf8dd728edc2b007535140bc09a566d9a4
Change-Id: Idb3c7406ede62a02123a7d4ea66e77dd107d4f47
…eprecated exception Change-Id: Ifc7babd679d157e6db20aa9a0c78b22188100fae
DDB store now has a special log s3guard.Operations which logs PUT/DELETE/TOMBSTONE calls with the application state; that state now has a counter to help provide context DumpS3GuardTable handles situation where a file isn't there when you look closer Change-Id: I49e0e65d6a65adbdf4ec048484bf323a9332d89e
This code is changed based on the hypothesis that it's been the pruning which has been rendering the store inconsistent in parallel test runs. Change-Id: Iab33d7eb57891f6ab92a12e4c75db12bfd794d75
…le rename speedups * The final cause of tombstones seems to be in ITestS3GuardListConsistency whose test files were appearing the most. Changes: * turn the FS into consistent mode before test teardown * explicitly delete the individually created files, so that in the rename() test we were guaranteeing that they were being deleted Made the turning back on of the rename speedup features a compile time option; turned back on, tests are happy. Planning more retests of this to see that all has gone quiet. Change-Id: If341687a1cbdc905782862f36b473faa9a0df84c
* reinstate all the disabled HADOOP-15183 ancestor caching * Add a test to explicitly verify that renaming an empty dir removes the marker from S3 * compare with trunk to reduce difference * Add javadocs on new dump and purge classes Change-Id: I80abc8e022a92bbb163226aa4dfa6ef80fcc2b0e
Change-Id: I13734049ddabdf3a451c906ca3fd2780d4b49c51
* summary prints the results * use queues to do the treewalks Change-Id: I4544ace79a5f004141bd81f0fb7a1849fa4b89c0 ITestS3GuardListConsistency: isolates an intermittently failing test within its own subtree ITestS3GuardRootOperations: turn on the pruning
* AbstractITCommitMRJob disables FS caching * ITestS3GuardDDBRootOperations disables some superfluous calls which added ~30s to the runtime Change-Id: Ic5b5f7bdd509f0fbaeb4b7d578a3060515e3b963
…stic Change-Id: I3a7bd5a76d1bb24d1a8d66a694310f065b5826c4
With the S3Guardroot operations test, there's no need to have a test of the Dump operation in ITestS3GuardToolDynamoDB; all it does is trigger test timeouts over slow network connections. Prune tool usage entry had "tombstone" entry in wrong place and without the leading "-" Change-Id: Ib71fcf077d407bc1ea5b333044fbb68c86642921
…tion (for yetus) Change-Id: I3652f2da54e6543dd7e2fa556d50b6b570db5b42
80e6157
to
d6f1241
Compare
Update:
|
💔 -1 overall
This message was automatically generated. |
checkstyles are invalid or, in the case of an intentation one, incorrect. |
Unit test failure looks like there was a mismatch between hadoop-common and hadoop-aws builds, as this is the test which HADOOP-16357 changed. The line at fault != the current source either.
|
Tests run locally, |
I'll test this against Ireland and report back with the results. Thanks for working on this @steveloughran ! |
🎊 +1 overall
This message was automatically generated. |
tested against ireland:
otherwise one timeout not related to this. |
I created a jira for the testMRJob failures as I'm the one who gets it - I should fix it. |
thanks. Gabor, you do explicitly need to do that +1 for the record |
+1; these improvements will make the s3a more stable. |
thanks for all the testing -committed to trunk |
…ed on if log4j or log4j2 is class-loaded Removing job.diagnostics.appender.class config, and populating it based on if log4j or log4j2 is class-loaded, defaults to assuming log4j. Author: Ray Matharu <rmatharu@linkedin.com> Reviewers: Prateek Maheshwari <pmaheshwari@apache.org> Closes apache#1003 from rmatharu/simplifying-diagnostics-config
Step one: a new root test to execute prune against the live store and DDB table.
To follow: debug the conditions leading to prune fail on my store :)
Change-Id: I25d138ed7b42f2b5eda12c2cd736f8c054b69820