Andrew Wong

Looked at https://ci-artifacts.dev.vectorized.cloud/redpanda/42577/018c5cd0-0abd-4319-af6a-3a479f61f53b/vbuild/ducktape/results/final/CloudStorageTimingStressTest/test_cloud_storage/cleanup_policy=compact.delete/70/RedpandaService-0-281472799218544/ Client side at a certain point, we see several attempts to connect, but they're immediately shut down ``` time="2023-12-12T07:23:26Z" level=debug msg="Calling PollFetches (lwm=[1218] status {\"name\":\"\",\"valid_reads\":1250,\"invalid_reads\":0,\"out_of_scope_invalid_reads\":0,\"max_offsets_consumed\":{\"0\":1349}})" time="2023-12-12T07:23:26Z" name=KgoVerifierSeqConsumer-0-281471353003584[DEBUG]...

Marking sev/high since this results in a stuck consumer. Looking at https://ci-artifacts.dev.vectorized.cloud/redpanda/43310/018c9296-a767-47d6-9645-d7176cee188e/vbuild/ducktape/results/final/CloudStorageTimingStressTest/test_cloud_storage/cleanup_policy=delete/97/ Similar to above, there are a bunch of `is SASL missing?` logs in the consumer logs. This time...

Here's a more complete sequence of a download failure: ``` DEBUG 2023-12-22 18:06:54,960 [shard 1:main] cluster - partition.cc:661 - timequery (cloud) {kafka/test-topic/0} t={timestamp: 1703268307239} max_offset(k)=15360 DEBUG 2023-12-22 18:06:54,960 [shard 1:main]...

https://drive.google.com/file/d/1wZnmolWJW0_ks4iiyZ74Z7w-dsTezLZy/view?usp=sharing Here are the logs, in case the above ones get lost

It appears that timequeries just aren't taking into account the archive start offset. From the above logs: Here's a given cursor. `begin` refers to the archive clean offset, though it...