Open cscorley opened 3 years ago
Great find! Thanks @cscorley !
@cscorley can you try with v21.8.1-beta4 image. We have a new release coming Tuesday with a ton of fixes in this area
@senior7515 I actually was able to also try this on the v21.8.1-beta5
image late yesterday. Same result.
Thanks. Looking into this.
Is this specific to rpk or for all clients? It's possible rpk was not configured to reset properly on out of range errors. A bunch of changes for rpk have gone in that should handle this case correctly now. We can try to recreate the above in rpk, but if the issue is resolved, we'll close this issue.
I was able to reproduce this on several clients, as stated above. My example used rpk to allow your team to reproduce yourselves. We have chosen not to use Redpanda, so I will not be testing this. Thanks!
Hi team,
Ran into an odd issue while experimenting with the
retention.ms
topic configuration. The issue is setting an absurdly low retention time (10sec) and restarting redpanda seems to create a state whererpk topic consume
does not work. For this, I am using docker compose. I don't think that's necessary to reproduce, but I have not tried it any other way :)I don't plan to use a
retention.ms
this low, but I was trying to find out what happens when the topic has one without having to wait for my desiredretention.ms
time (1 day).I don't believe this is the same as issue #340. Whenever I encounter this, the error is always
Reader cannot read before start of the log n-1 < n
. This issue also impacts other clients I am trying to use, and not justrpk topic consume
.Description and reproduction steps follow.
docker-compose.yml
bug.sh
Output from running above script (including my inputs to produce):
I have also tried specifying --offset.
--offset oldest
continues to fail with the above EOF message, while--offset newest
does not (and consumes new messages produced).On occasion, the error will be this at first (I have not been able to find repro for it):
Got an error consuming topic 'test', partition 0: kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
docker compose logs
JIRA Link: CORE-723