-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-15999 S3Guard OOB: improve test resilience and probes #630
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
Conversation
|
Tested: S3 ireland w/ DDB in both parallel and standalone runs, DDB set up for PAYG. I've not seen the problem surface again. Now, it could still be there, but I've gone through the tests line-by-line trying to think where stabilisation problems could surface, and I think it'll be ok. the only variable would be "how to allow for stabilisation?". I've chosen 2000 just for something non-zero-but not to slow down tests. We could up that to, say, 10s. Or actually play games with eventually, repeatedly calling getFileStatus until the modtime actually increased. |
|
💔 -1 overall
This message was automatically generated. |
|
Gabor: have a look at the patch, make sure it works for you, with DDB as the store, rather than just local. if you are happy with my changes, I'll do another run, and if all is well, give it a vote up |
(cherry picked from commit 5c78e44) Change-Id: I34ed39a82893ed2f1caed8ac80609075a68dec57
* Add delays long enough for timestamps to be different * Add delays for S3 to stabilize after writes/deletes, so that listings and HEAD calls will get the new value, not old ones * probes for differences look for file lengths ahead of timestamps, for more tangible failures. * and they validate the raw FS status acquired after the stabiliziation delay * package private (currently) probe for S3A to verify that an FS instances considers its store to be authoritative. Currently we've been checking the config, but to really know what's happening: lets query the internal state of FS. Change-Id: Ib0184a2aacbec1e4b316cb8cad0265bd0b579bcd
5aba1e4 to
4067561
Compare
|
💔 -1 overall
This message was automatically generated. |
|
failed tests are about a directory not existing on the test VM/container |
Use eventually() to await status changes in files: creation, deletion, overwrites. Allows 20s for state to change, wrapping * getFileStatus() calls on new file (swallowing IOEs until happy) * getFileStatus() on deleted files, expecting FNFEs to eventually surface * the checks for changed files in the overwrite tests. Change-Id: Ia128ebe4e1dc02f904794966b7a51f6ad91dd50f
|
Updated test with eventually called around operations where eventual consistency is possible, including some of the assertions. The only thing isn't checked is the s3guard list operations. Tested: S3 ireland with DDB, standalone and in parallel runs |
|
🎊 +1 overall
This message was automatically generated. |
|
Checkstyle |
|
Tested against ireland. Found one flaky/intermittent race condition issue fixed in https://issues.apache.org/jira/browse/HADOOP-16186. Otherwise it looks good. |
…hich will be committed, once my local test run completes Change-Id: I448d74af1914b3037a661dd8d2048846ebe22891
|
OK, if it works for you, I'm +1 too. fixing up the checkstyles and rerunning the tests before I do the final commit. |
… IR as input This PR has the following changes: - Let QueryTranslator take Calcite IR as input - Include 'INSERT INTO' sql statement for Calcite plan - Basic DSLConverter Framework with SamzaSQL dialect as an example - Some fixes to stream-table join wrt Serde Author: Aditya Toomula <[email protected]> Reviewers: Srinivasulu <[email protected]>, Weiqing <[email protected]> Closes apache#630 from atoomula/dsl3 and squashes the following commits: 93c66cee [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 21c0175b [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 15a1e9fb [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 5bf0c7e1 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 98cd9777 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 63a66fb1 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 6794b512 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. c9d434a9 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 94e53b64 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input. 30c76ed9 [Aditya Toomula] Samza SQL: Code re-org to accomodate Samza SQL engine to take Calcite IR as input.
HADOOP-15999 improve test resilience and probes
Currently we've been checking the config, but to really know what's happening: lets query the internal state of FS.
Change-Id: Ib0184a2aacbec1e4b316cb8cad0265bd0b579bcd
This is PR #624 with another patch applied