Flume
  1. Flume
  2. FLUME-1073

Default Log4j configuration file should have a rolling policy

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v1.1.0
    • Fix Version/s: v1.2.0
    • Component/s: None
    • Labels:
      None
    • Release Note:
      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.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Mike Percy
              Reporter:
              Arvind Prabhakar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development