Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-14515

Specifically configure zookeeper-related log levels in KMS log4j

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.0
    • Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
    • Component/s: kms
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      When investigating a case, we tried to turn on KMS DEBUG by setting the root logger in the log4j to DEBUG. This ends up making org.apache.zookeeper.ClientCnxn to generate 199.2M out of a 200M log file, which made the kms.log rotate very quickly.

      We should keep zookeeper's log unaffected by the root logger, and only turn it on when interested.

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment