Asias He

What is the result when this does not happen for dpdk?

@slivne Jenkins result suggestions we can close this issue as well.

I used tcp_server rxrx test + debug print. DPDK were dropping some packets. Only seq=2925 and seq=11401 of the data packets are received and passed from eth to ip/tcp. We...

Added more debug print in dpdk_qp::process_packets(). We did not see other data packets in dpdk_qp::process_packets() neither. And we do did drop packet because of ip or tcp csum error. ```...

Changes in 7e6a05f8675ffa17f3259d02f11199468d6dfd88: - Add missed space

The repair follower node failed to write rows ``` Sep 05 14:51:43 rolling-upgrade--debian-bullseye-db-node-e1d6ddc9-0-1 scylla[146264]: [shard 3] repair - repair[426d1799-bb87-4c00-98c7-4af35827ca7b]: shard=3, keyspace=scylla_bench, cf=test, range=(-4233469355322020765, -4229514567880051100], got error in row level repair:...

> @asias ping I don;t understand what you wrote in the above - what can we do to move forward here We need to bisect to find the problematic commit...

> i listed the commits between 5.0.2 (that passed without pain, to 5.0.3 and i found this list: Fabio, the test passed with 5.0.2 and started to fail with 5.0.3?...

I tried to reproduce locally with the 5.0.2-20220807.299122e78 and 5.1.0~rc1-0.20220902.d10aee15e7e9 as a mixed cluster + repair. I could not reproduce repair failure.

> @asias , how can we make progress from here? should we start building images with 5.0.3 without these commits and run reproducers? cc @slivne @eliransin I suggest moving the...