John Spray

The client manages to trip an offset_out_of_range by trying to fetch offset -1 here: Server sees: ``` TRACE 2022-10-05 17:54:38,947 [shard 1] kafka - requests.cc:89 - [172.16.16.21:35433] processing name:fetch, key:1,...

Here's an OffsetForLeaderEpoch sending an incorrect end_offset=-1 response (one of the things fixed in #6400) ``` TRACE 2022-10-05 17:54:38,941 [shard 0] kafka - request_context.h:154 - [172.16.16.21:35407] sending 23:offset_for_leader_epoch response {throttle_time_ms=0...

When 21.1.8 is release (currently at rc1) this issue should be fixed.

Hasn't reocurred since we released 21.1.8

> Should we also validate this while setting topic properties in AlterConfiguration ? The thinking behind the silent clamping is: - someone might have an existing app/script/tool that expects to...

Force pushed to fix the new test (it wasn't clearing the properties at end of test, which caused other tests to misbehave) Twiddling global configs in tests is a bit...

The test needed updating again because I wasn't taking account of segment size jitter (nothing is ever simple!) This is the second time that jitter has bitten me when trying...

Same https://buildkite.com/redpanda/redpanda/builds/15710#01837966-9d28-4a71-9d6a-5d65fc9d7aac

This is ready to be rebased now that Vlad's PR merged

``` ^[[0m[ERROR:2022-11-01 12:09:02,525]: Failed to import rptest.tests.retention_policy_test, which may indicate a broken test that cannot be loaded: ImportError: cannot import name 'S3View' from 'rptest.utils.si_utils' (/root/tests/rptest/utils/si_utils.py)^M ```