[Bug]: download-server returns 504 on timeouts from metadata service, aborting sector import by boost

[parkan]

Description

In cases where the singularity metadata API is too slow to return a response to HEAD from the download-server boost will receive a 504 response and the sector import will abort with a data-transfer error:

Error: data-transfer failed: http HEAD req failed: code: 504, status: 504 Gateway Timeout

In itself this wouldn't be catastrophic, but from boost's perspective this error is considered non-recoverable and the deal will be in limbo until either the start delay runs out or the client forces a retry.

The ameliorations that I see are to increase the timeout value in download-server, make it configurable, add exponential retry (also configurable, ideally), or otherwise increase download-server tolerance of slow initial response

Steps to Reproduce

• attempt to import a sector from singularity with a slow DB backend

Version

v0.5.16

Operating System

Linux

Database Backend

PostgreSQL

Additional context

No response