Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-17122

Failed to release WAL segments even after reaching DataStorageConfiguration#maxWalArchiveSize

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.13
    • None
    • persistence
    • None
    • Docs Required, Release Notes Required

    Description

      When maxWalArchiveSize is reached, Ignite is able to detect that and tries to release WAL segments (and prints out "maximum size of the WAL archive exceeded, the segments will be forcibly released"). However the WAL archive deletion doesn't happens immediately, and sometimes it happens almost 1 hour after the first detection, and the actual WAL archive size is much larger than the maxWalArchiveSize. See the (trimmed) attached log for an example.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              marcus.lo Marcus Lo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: