Fdbbackup expire timing out

Using FoundationDB
1

Hi,

often when attempting to perform a fdbbackup expire call to purge all backups, the call fails with an error indicating a time out when in the Describing backup or Listing files phase. There is no alternative than to retry the call over and over again until it goes through.

Is there a knob that can be tuned to increase the time out or force fdbbackup to perform multiple attempts?

2

Found out the timeouts could be modified in the blobstore URL, using the connect_tries, connect_timeout and request_timeout_min parameters. That did the trick.

2 Likes