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

Broker should not set leader epoch if the list-offset request version < 4

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.6.0
    • Fix Version/s: 2.7.0
    • Component/s: core
    • Labels:
      None

      Description

      The list-offset response added a new field in version 4:

              { "name": "LeaderEpoch", "type": "int32", "versions": "4+" }
      

      And the compiled code would throw UnsupportedVersionException if that field is not default (-1) with version < 4. However, on the broker side we forget to add the logic to not setting this field based on the request version. This would cause old versioned clients' list-offset call to always get UnsupportedVersionException and an empty result would be returned.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: