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

Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1
    • Fix Version/s: 0.10.2.0
    • Component/s: None
    • Labels:
      None

      Description

      When all the members in a consumer group have died and all of its offsets have expired, we write a tombstone to __consumer_offsets so that its group metadata is cleaned up. It is possible that after this happens, the same groupId is then used only for offset storage (i.e. by "simple" consumers). Our current cache loading logic, which is triggered when a coordinator first takes over control of a partition, does not account for this scenario and would currently fail.

      This is probably an unlikely scenario to hit in practice, but it reveals the lack of test coverage around the cache loading logic. We should improve this.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hachikuji Jason Gustafson
                Reporter:
                hachikuji Jason Gustafson
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: