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

GroupMetadataManager ignores current_state_timestamp field for GROUP_METADATA_VALUE_SCHEMA_V3

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.1.1, 2.2.2, 2.4.1, 2.6.0, 2.5.1
    • Fix Version/s: 2.3.2, 2.4.2, 2.7.0, 2.5.2, 2.6.1
    • Component/s: offset manager
    • Labels:
      None

      Description

      While reading group metadata information from ByteBuffer GroupMetadataManager reads current_state_timestamp only for group schema version 2. For all other versions this value is set to "None". 

      Piece of code responsible for the bug:

      https://github.com/apache/kafka/blob/2.6.0/core/src/main/scala/kafka/coordinator/group/GroupMetadataManager.scala#L1412

      Restarting kafka forces GroupMetadataManager manager to reload group metadata from file basically causing [KIP-211|https://cwiki.apache.org/confluence/display/KAFKA/KIP-211%3A+Revise+Expiration+Semantics+of+Consumer+Group+Offsets] to be only applicable for schema version 2. 

       

       

        Attachments

          Activity

            People

            • Assignee:
              showuon Luke Chen
              Reporter:
              the.paczek Marek

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment