[
https://issues.apache.org/jira/browse/HADOOP-19664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016563#comment-18016563
]
ASF GitHub Bot commented on HADOOP-19664:
-----------------------------------------
ahmarsuhail opened a new pull request, #7909:
URL: https://github.com/apache/hadoop/pull/7909
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Moves AAL to use the Java sync client as this is giving us the best
performance in internal benchmarks.
### How was this patch tested?
Tested in
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> S3A Analytics-Accelerator: Move AAL to use Java sync client
> -----------------------------------------------------------
>
> Key: HADOOP-19664
> URL: https://issues.apache.org/jira/browse/HADOOP-19664
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.5.0
> Reporter: Ahmar Suhail
> Priority: Major
>
> Java sync client is giving the best performance for our use case, especially
> for readVectored() where a large number of requests can be made concurrently.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
