Denis Rystsov
Denis Rystsov
The logs also have this record: ``` [WARNING - 2022-05-11 07:08:19,191 - service_registry - stop_all - lineno:55]: Error stopping service : VerifiableConsumer-0-140554673463360-worker-1: Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/ducktape/services/background_thread.py", line...
https://github.com/redpanda-data/redpanda/pull/5238 introduces a new workload & online verifier which isn't subject to such errors when it's it we switch to it and it will fix this issue
Another instance - https://buildkite.com/redpanda/redpanda/builds/14417#0182b82f-a440-4ab7-9da4-267e358d8428
Another instance https://buildkite.com/redpanda/redpanda/builds/14540#0182c846-5775-4635-b17f-6b7a9535171f
> it looks a lot like the server really is leaving a gap in the kafka offsets ... It's not clear to me that this is valid behavior in redpanda....
Interesting so we have several issues hidden behind the "Consumer failed to consume up to offsets" umbrella
> Trying to wrap my head around KIP-360 proposal. We don't need to implement the section on `Prolonged producer state retention` because we already keep that state for 7d since...
Something is failing
tests are failing > Failed to import rptest.tests.transactions_test, which may indicate a broken test that cannot be loaded: NameError: name 'RESTART_LOG_ALLOW_LIST' is not defined
Another instance https://buildkite.com/redpanda/redpanda/builds/14311#0182b1e9-cd33-421b-a908-d7400ba039df