gaborgsomogyi commented on PR #28236: URL: https://github.com/apache/flink/pull/28236#issuecomment-4543578507
\`StandardRetryStrategy\` is the SDK's recommended general-purpose strategy, which is the primary reason for this choice. Beyond that, the SDK's own documentation explicitly cautions against \`AdaptiveRetryStrategy\` when a single client serves multiple resources: *"throttling or outages associated with one resource will result in increased latency and failures when accessing all other resources via the same client."* Flink's S3 client is shared across concurrent operations (checkpoint writes, reads, metadata calls), so adaptive mode's rate limiter would cause throttling on one operation to bleed into unrelated ones. \`StandardRetryStrategy\` is the right fit here. -- 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]
