Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-10990

Get rid of per-osc max_dirty_mb setting

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • Lustre 2.12.0
    • None
    • None
    • 9223372036854775807

    Description

      max_dirty_mb is an ages old kludge we had to ensure faster flushing that avoided various timeouts, limits on memory consumption and limits on data lost should the ost run out of space.

      All of those now have proper mechanisms: we have grants to ensure nothing runs out of space, we have per-node dirty and clean pages limits and we have lock prolongation for active IO.

      As such I believe we no longer need the max_dirty_mb

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. LU-11157 sanity test_42e: invalid arithmetic operator (error token is ".9")

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-8708 Grant shrinking disabled all the time

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              green Oleg Drokin
              green Oleg Drokin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: