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

Some INFO level logging needs to be DEBUG

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None

    Description

      Some of the INFO level log4j entries are not really useful, for example in SocketServer.Processor, due to metadata requests that reply on a separate and short-lived socket, the following log can be constantly printed:

      info("Closing socket connection to %s.".format(channelFor(key).socket.getInetAddress))

      We'd better move them to DEBUG if they are expected in normal state.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-1591 Clean-up Unnecessary stack trace in error/warn logs

          • Major - Major loss of function.
          • Patch Available
          is related to

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-10060 Kafka is logging too verbosely at the INFO level

          • Major - Major loss of function.
          • Open

          Activity

            People

              mgharat Mayuresh Gharat
              guozhang Guozhang Wang
              Guozhang Wang Guozhang Wang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: