Metadata writeback cache support
(LU-10938)
|
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Technical task | Priority: | Minor |
| Reporter: | Qian Yingjin | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
Under WBC, all metadata and data are cached in MemFS, not being flushed to MDT and OSTs. To void running out of the server space, it needs to design a grant mechanism similar to current OST space grant to control inodes grant from MDT.
|
| Comments |
| Comment by Andreas Dilger [ 16/May/20 ] |
|
As a general rule, it is much more efficient to keep subdirectory trees on a single MDT, since this avoids expensive cross-MDT transactions. The good thing with metadata vs. data, is that it is relatively easy to change over to a new MDT if one is getting full by creating a remote directory entry. There is already a protocol for OSTs to grant clients space for data at connect time, and the same should be used for grant from the MDTs. Since DoM is using the OST read/write protocol to the MDS, it should be possible to use this for data grant, but some changes may be needed to add in metadata grant (e.g. inodes). As for MDT/OST selection, the client already has "LMV QOS" logic for directory selection with "lfs mkdir -i -1" so this can be reused ( |
| Comment by Gerrit Updater [ 01/Aug/22 ] |
|
"Yingjin Qian <qian@ddn.com>" uploaded a new patch: https://review.whamcloud.com/48099 |