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

Get rid of per-osc max_dirty_mb setting

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Lustre 2.12.0
    • Labels:
      None
    • Rank (Obsolete):
      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

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: