Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GCS Backup times out at 120s

Open
#771 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
google-cloud, kubernetes, postgresql

Research direction

Start from the barman-cloud-backup command's Google Cloud Storage upload path and trace where the 120-second timeout is set. Compare that value with --read-timeout and verify how a slow upload is handled. Done means the configured timeout controls the upload operation and the reported timeout behavior is covered by appropriate tests.

Written by the indexing model from the issue text.

Description

bug

We have kubernetes clusters at remote locations that are connected to the cloud via slow connections. The database size is also small (approx 40MB compressed). However the upload to GCS buckets is timing out. Despite setting the --read-timeout to 600, it times out after 120s.

The command used is as follows
barman-cloud-backup --user postgres --name <name>--gzip --read-timeout 600 --cloud-provider google-cloud-storage gs://<gcs bucket/folder> <cluster name>

The error is as follows
ERROR: <class 'google.api_core.exceptions.RetryError'>
ERROR: Timeout of 120.0s exceeded, last exception: ('Connection aborted.', timeout('The write operation timed out'))
ERROR: Upload error: Timeout of 120.0s exceeded, last exception: ('Connection aborted.', timeout('The write operation timed out')) (worker 0)

It looks like the timeout is hard coded and cannot be changed. I have also tried setting the read-timeout to 0 without any success.

Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 7h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/plugin-barman-cloud

All issues in cloudnative-pg/plugin-barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.