Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-1326 New consumer checklist
  3. KAFKA-1925

Coordinator Node Id set to INT_MAX breaks coordinator metadata updates

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.0.0
    • Component/s: consumer
    • Labels:
      None

      Description

      KafkaConsumer used INT_MAX to mimic a new socket for coordinator (details can be found in KAFKA-1760). However, this behavior breaks the coordinator as the underlying NetworkClient only used the node id to determine when to initiate a new connection:

      if (connectionStates.canConnect(node.id(), now))
                  // if we are interested in sending to a node and we don't have a connection to it, initiate one
                  initiateConnect(node, now);
      

        Attachments

        1. KAFKA-1925.v1.patch
          2 kB
          Guozhang Wang

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: