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

Metadata not updated when consumer encounters FENCED_LEADER_EPOCH

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.3.0
    • Fix Version/s: 2.5.0, 2.3.2, 2.4.1
    • Component/s: None
    • Labels:
      None

      Description

      Inside the consumer Fetcher's handling of ListOffsetResponse, if we hit `FENCED_LEADER_EPOCH` on partition level, the client will blindly retry without refreshing the metadata, creating a stuck state as the local leader epoch never gets updated and constantly fails the broker check.

      The solution is to trigger metadata update upon receiving retriable errors, before we kick off another offset list.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bchen225242 Boyang Chen
                Reporter:
                bchen225242 Boyang Chen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: