Data-on-MDT phase II (LU-10176)

[LU-13415] DoM: keep optimizations even when OST stripe is initialized Created: 06/Apr/20  Updated: 14/May/20  Resolved: 14/May/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.14.0

Type: Technical task Priority: Minor
Reporter: Mikhail Pershin Assignee: Mikhail Pershin
Resolution: Fixed Votes: 0
Labels: None

Rank (Obsolete): 9223372036854775807

 Description   

Some DoM optimizations like read-on-open or IO-lock-on-open are being used only when OST stripes are non-initialized, supposing that it makes a little sense otherwise. Meanwhile, OST stripe can be initialized by a first append to the DOM file, so that is not good indicator to stop using DOM benefits. File can stay small and with just MDT stripe used for a long time after that. Ideally that would be to stop using DoM only when OST objects have non-zero size but that is not easy to figure out from MDT.
Nevertheless, it is not big deal to use read-on-open and IO-lock-at-open features even for files with OST data with few extra checks, e.g. don't use read-on-open if MDT stripe is full and take IO lock at open optionally in 'try' mode.



 Comments   
Comment by Gerrit Updater [ 07/Apr/20 ]

Mike Pershin (mpershin@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/38152
Subject: LU-13415 dom: use DoM optimization for DOM+OST files
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 498337e19e62a3d7fea5eb2f2835f41284ccb663

Comment by Gerrit Updater [ 14/May/20 ]

Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38152/
Subject: LU-13415 dom: use DoM optimization for DOM+OST files
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 067dc642521487b2d53f46da1dec4b9d5f570c67

Comment by Peter Jones [ 14/May/20 ]

Landed for 2.14

Generated at Sat Feb 10 03:01:04 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.