[LU-10990] Get rid of per-osc max_dirty_mb setting

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0
• Assignee: Oleg Drokin
• Reporter: Oleg Drokin

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

Issue Links

• is related to: LU-11157 sanity test_42e: invalid arithmetic operator (error token is ".9")
• is related to: LU-8708 Grant shrinking disabled all the time

Comments

[Peter Jones]

Landed for 2.12

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/32288/
Subject: LU-10990 osc: increase default max_dirty_mb to 2G
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 92e2b514e06ca2cd8c83e7439e206a629ba508f2

[Gerrit Updater]

Oleg Drokin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/32288
Subject: LU-10990 osc: increase default max_dirty_mb to 1G
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 64bcc00c140c46462fb6536423a1b7c0c619c49e

[Gerrit Updater]

Oleg Drokin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/32252
Subject: LU-10990 osc: Get rid of max_dirty_mb
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 367092b3d8716ab2bc870a20ac8985403e160484