[
https://issues.apache.org/jira/browse/HADOOP-19399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921495#comment-17921495
]
ASF GitHub Bot commented on HADOOP-19399:
-----------------------------------------
steveloughran commented on PR #7333:
URL: https://github.com/apache/hadoop/pull/7333#issuecomment-2616589587
I'd like a single CRT on/off switch, rather than a separate client for AAL
Create/destroy of a client is expensive, hence the move to lazy creation.
Even with that, fs close() times get worse. Threads and the connection pool are
key factor .
We need those shared thread and connection pools, not just for those
overheads, but so that we can have warm pools of both waiting for new requests
coming in.
We don't want to make things worse there.
Equally critical is test coverage: being able to turn it on for the single
client makes it possible to run the entire ITest suites against it. Ideally a
`-Pcrt` switch could be added to maven to turn this on and off, and we can add
it to the test matrix for release qualification
> S3A: Add support for CRT client
> -------------------------------
>
> Key: HADOOP-19399
> URL: https://issues.apache.org/jira/browse/HADOOP-19399
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.1
> Reporter: Ahmar Suhail
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.2
>
>
> * Allow ClientManager to initialise a CRT client
> * Should be optional, java async client to still be supported as default
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
