Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-1073

Default Log4j configuration file should have a rolling policy

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.1.0
    • 1.2.0
    • None
    • None
    • If the user keeps the default log4j.properties in place, flume now logs to flume.log instead of stdout. This can be overridden on the command line by specifying an argument similar to the following: -Dflume.root.logger=DEBUG,console

    Description

      Flume Agents are expected to run for indefinite amount of time and will likely generate a lot of information via it's logs. As such, we need to have a log rolling policy in place to ensure that the system does not run out of disk space due to the log file sizes.

      Attachments

        1. FLUME-1073-2.patch
          2 kB
          Mike Percy

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. HADOOP-8149 cap space usage of default log4j rolling policy

          • Major - Major loss of function.
          • Closed

          Activity

            People

              mpercy Mike Percy
              aprabhakar Arvind Prabhakar
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: