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

Kafka server can become unavailable if clients send several metadata requests

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: None
    • Component/s: replication
    • Labels:
      None

      Description

      Currently, if a broker is bounced without controlled shutdown and there are several clients talking to the Kafka cluster, each of the clients realize the unavailability of leaders for some partitions. This leads to several metadata requests sent to the Kafka brokers. Since metadata requests are pretty slow, all the I/O threads quickly become busy serving the metadata requests. This leads to a full request queue, that stalls handling of finished responses since the same network thread handles requests as well as responses. In this situation, clients timeout on metadata requests and send more metadata requests. This quickly makes the Kafka cluster unavailable.

        Attachments

        1. metadata-request-improvement.patch
          91 kB
          Neha Narkhede
        2. kafka-901.patch
          117 kB
          Neha Narkhede
        3. kafka-901-v2.patch
          138 kB
          Neha Narkhede
        4. kafka-901-v4.patch
          133 kB
          Neha Narkhede
        5. kafka-901-v5.patch
          134 kB
          Neha Narkhede
        6. kafka-901-followup.patch
          4 kB
          Neha Narkhede
        7. kafka-901-followup2.patch
          5 kB
          Neha Narkhede

          Activity

            People

            • Assignee:
              nehanarkhede Neha Narkhede
              Reporter:
              nehanarkhede Neha Narkhede
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: