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

Extreme amounts of logging done by unauthorized Kafka clients

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • clients
    • None

    Description

      Having experimented some with custom authorization options for Kafka on the broker side, we have a bunch of clients that are no longer authorized. While that's expected and fine, we did not anticipate the level of logging that these unauthorized clients would spew out - putting our whole logging subsystem under heavy stress.

      The message log is similar to the one below:

      2019-11-25 10:08:10.262  WARN 1 --- [ntainer#0-0-C-1] o.a.k.c.consumer.internals.Fetcher       : [Consumer clientId=sdp-ee-miami-0, groupId=sdp-ee-miami] Not authorized to read from topic sdp.ee-miami.
      

      In just 4 hours this same message was repeated about a hundred million times ( ! ) in the worst offending client, 74 million times in the next one and 72 million times in the third.

      We will roll out customized burst filters to suppress this on the client loggers, but it would of course be best if this was fixed in the client.

      Attachments

        Activity

          People

            Unassigned Unassigned
            anderseknert Anders Eknert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: