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

Controller incorrectly logs rack information when new brokers are added

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.10.2.0, 0.10.2.1, 0.11.0.0
    • Fix Version/s: 0.11.0.0
    • Component/s: config, controller
    • Labels:
      None
    • Environment:
      Ubuntu Trusty (14.04.5), Oracle JDK 8

      Description

      When a new broker is added, on an UpdateMetadata request, rack information won't be present in the state-change log even if configured.

      Example:

      {{pri=TRACE t=Controller-1-to-broker-0-send-thread at=logger Controller 1 epoch 1 received response

      {error_code=0}

      for a request sent to broker <ip>:<port> (id: 0 rack: null)}}

      This happens because ControllerChannelManager always instantiates a Node using the same constructor whether or not rack-aware is configured. We're happy to contribute a patch since this causes some confusion when running with rack-aware replica placement.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jchao Jeff Chao
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: