konstantinb commented on PR #8426: URL: https://github.com/apache/hadoop/pull/8426#issuecomment-4796446796
I ran the full hadoop-aws integration suite with all four shared pools off, then on, matching the cloud_aws CI invocation (JDK 17; ./mvnw verify -B -Dparallel-tests -Dscale=true), against both LocalStack (the CI endpoint) and real S3 (us-east-1). - Correctness: identical failing-test set with pools off vs on, on both endpoints. The failures on my local are identical and appear environmental (community-LocalStack emulation gaps; STS/delegation/Kerberos/ACL setup on the test bucket) — none introduced by this change. - Performance: no measurable regression. Pools-on matched pools-off on runs identical to CI setup across repeated attempts, and on the operation-heavy real-S3 paths I measured directly (commit protocols, recursive treewalk, huge-file uploads). So, enabling the shared pools neither changes results nor measurably affects performance in these runs. Unless someone objects, I will flip the defaults to ON tomorrow and ask for reapprovals -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
