ben-roling commented on issue #675: HADOOP-16085: use object version or etags to protect against inconsistent read after replace/overwrite URL: https://github.com/apache/hadoop/pull/675#issuecomment-480949149 One more [commit](https://github.com/apache/hadoop/pull/675/commits/708c00167f8d9f416bcba120b9d1122f4e42947e) pushed dealing with the group field on S3AFileStatus. The commit comment explains it. I've run the full integration test suite twice on this - once with a bucket with object versioning enabled, and once with a bucket with object versioning disabled. I used the following command to execute the tests: ``` mvn -T 1C verify -Dparallel-tests -DtestsThreadCount=8 -Ds3guard -Ddynamo ``` In both cases, I did initially get a few test errors/failures caused by DynamoDB timeouts. The tests that exhibited this were: * ITestS3AContractGetFileStatusV1List (teardown(), testListLocatedStatusFiltering(), testListStatusFiltering(), testComplexDirActions(), testListStatusEmptyDirectory()) * ITestDynamoDBMetadataStore.testProvisionTable() * ITestS3GuardToolDynamoDB.testPruneCommandCLI() I followed the failure up by running each of those tests individually: ``` mvn -T 1C verify -Dtest=skip -Ds3guard -Ddynamo -Dit.test=ITestS3AContractGetFileStatusV1List mvn -T 1C verify -Dtest=skip -Ds3guard -Ddynamo -Dit.test=ITestDynamoDBMetadataStore mvn -T 1C verify -Dtest=skip -Ds3guard -Ddynamo -Dit.test=ITestS3GuardToolDynamoDB ``` All of those tests were successful. I'm assuming the failures were related to a combination of the concurrency and the provisioned DynamoDB capacity.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
