From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox v2 1/3] s3-client: early return when request timeout deadline reached
Date: Tue, 24 Feb 2026 14:49:42 +0100 [thread overview]
Message-ID: <20260224134944.593408-2-c.ebner@proxmox.com> (raw)
In-Reply-To: <20260224134944.593408-1-c.ebner@proxmox.com>
The optional timeout value generates a deadline, after which the
request times out and fails, independent from retries.
The current implementation however unneededly continues to loop over
the remaining retires, including potential put rate limit delay and
exponential backoff time, creating unjustified additional latency.
Fix this by early returning with error once the deadline is reached.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
changes since version 1:
- no changes
proxmox-s3-client/src/client.rs | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/proxmox-s3-client/src/client.rs b/proxmox-s3-client/src/client.rs
index 83176b39..5e30aa12 100644
--- a/proxmox-s3-client/src/client.rs
+++ b/proxmox-s3-client/src/client.rs
@@ -386,23 +386,20 @@ impl S3Client {
}
let response = if let Some(deadline) = deadline {
- tokio::time::timeout_at(deadline, self.client.request(request)).await
+ tokio::time::timeout_at(deadline, self.client.request(request))
+ .await
+ .context("request timeout reached")?
} else {
- Ok(self.client.request(request).await)
+ self.client.request(request).await
};
match response {
- Ok(Ok(response)) => return Ok(response),
- Ok(Err(err)) => {
+ Ok(response) => return Ok(response),
+ Err(err) => {
if retry >= MAX_S3_HTTP_REQUEST_RETRY - 1 {
return Err(err.into());
}
}
- Err(_elapsed) => {
- if retry >= MAX_S3_HTTP_REQUEST_RETRY - 1 {
- bail!("request timed out exceeding retries");
- }
- }
}
}
--
2.47.3
next prev parent reply other threads:[~2026-02-24 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 13:49 [PATCH proxmox v2 0/3] fix #6858: implement retry logic for transient API errors Christian Ebner
2026-02-24 13:49 ` Christian Ebner [this message]
2026-02-24 13:49 ` [PATCH proxmox v2 2/3] s3-client: move exponential backoff to after the response state check Christian Ebner
2026-02-24 13:49 ` [PATCH proxmox v2 3/3] fix #6858: s3-client: retry request on 500, 503 and 504 status codes Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260224134944.593408-2-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox