If a transfer (upload, download, or request) stalls, i.e., no bytes are sent or received for a significant period, it may be better to restart the transfer as this may indicate a network glitch. For downloads the google::cloud::storage::DownloadStallTimeoutOption takes precedence.
For large requests (e.g. downloads in the GiB to TiB range) this is a better configuration parameter than a simple timeout, as the transfers will take minutes or hours to complete. Relying on a timeout value for them would not work, as the timeout would be too large to be useful. For small requests, this is as effective as a timeout parameter, but maybe unfamiliar and thus harder to reason about.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This page details the `TransferStallTimeoutOption` for Google Cloud Storage, focusing on how it handles transfer stalls, where no data is moved for a long time."],["The latest version documented is 2.37.0-rc, with a range of previous versions down to 2.11.0 available for reference."],["The `TransferStallTimeoutOption` is more effective than a simple timeout for large transfers that may take hours to complete, like large downloads or uploads."],["The option defines the duration the system will wait without receiving or sending data before assuming there is a network problem and potentially restarting the transfer."],["The `TransferStallTimeoutOption` uses a `std::chrono::seconds` type alias to configure the time until timeout."]]],[]]
