search

redpanda-data / redpanda

Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
https://redpanda.com
9.74k stars 592 forks source link

Offset Value inconsistent with AK after transaction rollback #13364

Open JFlath opened 1 year ago

JFlath commented 1 year ago

Version & Environment

Redpanda version: (use rpk version): 23.2.8

What went wrong?

When rolling back a transaction, Redpanda exhibits correct functional behaviour wrt actual messages that can be consumed, however ends up reporting a committed offset 1 higher than AK.

What should have happened instead?

The same value should be reported for consistency across platforms.

How to reproduce the issue?

  1. Produce N messages in a transaction
  2. Rollback the transaction
  3. Check ListCommittedOffsets - obvserve that AK reports N+1 and RP reports N+2.

Additional information

https://redpandadata.slack.com/archives/C01ND4SVB6Z/p1694098547528039

JIRA Link: CORE-1440

github-actions[bot] commented 11 months ago

This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

alexstuckeyjump commented 11 months ago

Please keep this open

github-actions[bot] commented 3 weeks ago

This issue hasn't seen activity in 3 months. If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

alexstuckeyjump commented 3 weeks ago

Please keep this open

piyushredpanda commented 3 weeks ago

@alexstuckeyjump do you happen to have a reproducer or confirmation that this issue happens with latest versions? We have reworked our entire transactions subsystem in v24.2.x. Would you be able to give that a go and see if this is fixed already?