This is an automated email from the ASF dual-hosted git repository.

yiguolei pushed a commit to branch branch-4.1
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/branch-4.1 by this push:
     new 0b4eff14371 branch-4.1: [fix](cloud) set recycler S3 client 
requestTimeoutMs to avoid curl-28 on slow DeleteObjects (mirror #49315) #64758 
(#65804)
0b4eff14371 is described below

commit 0b4eff14371a65a6b0151431a5e3954496f5d488
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Jul 23 14:30:53 2026 +0800

    branch-4.1: [fix](cloud) set recycler S3 client requestTimeoutMs to avoid 
curl-28 on slow DeleteObjects (mirror #49315) #64758 (#65804)
    
    Cherry-picked from #64758
    
    Signed-off-by: Steven Pall <[email protected]>
    Co-authored-by: Steven Pall <[email protected]>
---
 cloud/src/recycler/s3_accessor.cpp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/cloud/src/recycler/s3_accessor.cpp 
b/cloud/src/recycler/s3_accessor.cpp
index 8ff29694bd7..0c90676d8e0 100644
--- a/cloud/src/recycler/s3_accessor.cpp
+++ b/cloud/src/recycler/s3_accessor.cpp
@@ -449,6 +449,11 @@ int S3Accessor::init() {
         if (!_ca_cert_file_path.empty()) {
             aws_config.caFile = _ca_cert_file_path;
         }
+        // Mirror BE PR #49315: default ClientConfiguration leaves 
requestTimeoutMs=3000,
+        // which the vendored aws-sdk-cpp maps to CURLOPT_LOW_SPEED_TIME=3 and 
causes
+        // curl error 28 on slow/large S3 DeleteObjects (OVH cold vault).
+        aws_config.requestTimeoutMs = 30000;
+        aws_config.connectTimeoutMs = 5000;
         auto s3_client = std::make_shared<Aws::S3::S3Client>(
                 get_aws_credentials_provider(conf_), std::move(aws_config),
                 Aws::Client::AWSAuthV4Signer::PayloadSigningPolicy::Never,


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to