Large PITR binlog uploads to Azure storage timeout with "Context deadline exceeded"

[dcaputo-harmoni]

Report

When uploading large (1GB) binlog files to Azure, the UploadStream times out with the error "Context deadline exceeded". Realized that the default (max) concurrency for UploadStream is 1, which is too low for large uploads. Increased this to 4 and the problem went away. Will submit PR with the change.

More about the problem

Unfortunately did not capture the failure error before I pushed the fix to my local environment, but basically the binlog upload from the PITR container was stuck / failing on a large binlog file with "Context deadline exceeded" as the error.

Steps to reproduce

Enable PITR with Azure storage and a large binlog file.

Versions

1. Kubernetes 1.30.4
2. Operator 1.15.0
3. Database 1.15.0

Anything else?

No response