Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-266

FixedWindowRollingPolicy MAX_WINDOW_SIZE too small?


    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.12
    • Component/s: logback-core
    • Labels:
    • Environment:

      Operating System: Windows
      Platform: All

    • Bugzilla Id:


      I know it's not a blog but let me first say I've switched from log time use of JCL / log4j and think SLF4J / Logback is awesome so kudos to you guys for getting this out here... simple and powerful.. not much to not like

      I'm curious as to why a window size as small as 12 was chosen here. I realize the renaming of all files within the window gets more expensive as the window increases but it seems prohibitive for people with larger logging requirements. Moreover, the fact that it is final means I can't override this either although I realize it is rather trivial to build my own implementation.

      I have a project that generates a tremendous amount of logging currently (about 100MB every 6 minutes) and in my current setup have issues with files over 2GB. With the current MAX_WINDOW_SIZE I can only keep a days worth of logs!

      If the rename is a big deal a rolling policy that just uses the index as a cyclic sequence should work fine or are there other reasons to cap this at something so low?

      I could submit an implementation back if you like but just curious to get your feedback and any reasoning I might be missing on keeping the window size so low.

      Thanks again for a great product!




            • Assignee:
              logback-dev Logback dev list
              michael_mansell@yahoo.com Mike Mansell
            • Votes:
              4 Vote for this issue
              5 Start watching this issue


              • Created: