Joonas Koivunen 0acb604fa3 test: no missed wakeups, cancellation and timeout flow to downloads (#7863) ...

I suspected a wakeup could be lost with
`remote_storage::support::DownloadStream` if the cancellation and inner
stream wakeups happen simultaneously. The next poll would only return
the cancellation error without setting the wakeup. There is no lost
wakeup because the single future for getting the cancellation error is
consumed when the value is ready, and a new future is created for the
*next* value. The new future is always polled. Similarly, if only the
`Stream::poll_next` is being used after a `Some(_)` value has been
yielded, it makes no sense to have an expectation of a wakeup for the
*(N+1)th* stream value already set because when a value is wanted,
`Stream::poll_next` will be called.

A test is added to show that the above is true.

Additionally, there was a question of these cancellations and timeouts
flowing to attached or secondary tenant downloads. A test is added to
show that this, in fact, happens.

Lastly, a warning message is logged when a download stream is polled
after a timeout or cancellation error (currently unexpected) so we can
rule it out while troubleshooting.

2024-06-04 14:19:36 +03:00

..

src

test: no missed wakeups, cancellation and timeout flow to downloads (#7863)

2024-06-04 14:19:36 +03:00

tests

Ability to specify the upload_storage_class in S3 bucket configuration (#7461)

2024-04-24 18:48:25 +02:00

Cargo.toml

Use streaming downloads for Azure as well (#7579)

2024-05-02 20:19:00 +02:00