Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-7042

Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: consumer
    • Labels:
      None

      Description

      When READ_COMMITTED is turned on (since 0.11.0), LIST_OFFSET requires min_version to be 2 on the consumer client side. On the other hand, if broker is no newer than 0.10.2 it can only recognize the version of LIST_OFFSET up to 1. In this case the consumer talking to such an old broker will throw an exception right away.

      What we can improve though, is that when the consumer realized broker does not recognize LIST_OFFSET of at least 2, it can fall back to the old behavior of READ_UNCOMMITTED since the data on that broker should not have any txn markers anyways. By doing this we would lift the hard restriction that consumers with READ_COMMITTED cannot work with an older version of broker (remember we are trying to achieve broker compatibility since 0.10.0).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              guozhang Guozhang Wang
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: