[LU-15011] implement lod pool spilling Created: 16/Sep/21  Updated: 08/Aug/23  Resolved: 26/Nov/21

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

Type: Improvement Priority: Minor
Reporter: Andreas Dilger Assignee: Alex Zhuravlev
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
Related
is related to LUDOC-517 add pool_spill parameters to manual Open
is related to LU-15072 Pool spill is activated just by chang... Resolved
is related to LU-15043 OST spill pools should not allow spil... Resolved
is related to LU-13058 Intermediate component removal (PFL/SEL) Open
Rank (Obsolete): 9223372036854775807

 Description   

If an OST pool becomes full, allow configuring a global default spill target to hold files that could not be written due to the pool running out of space. This is similar to SEL, but implemented at the pool selection level, rather than on a per-write basis. While SEL is probably flexible (essentially it implements pool spill on a per-component basis), very few users know enough about SEL to use it effectively, and any changes to the SEL configuration would require updating every file that is using a particualr SEL layout. In contrast, pool spill is a tunable on the MDS (for each source pool) and affects all existing layouts using that pool if there is a spill target pool and used space threshold specified.



 Comments   
Comment by Andreas Dilger [ 16/Sep/21 ]

Originally submitted as LU-14825, but that issue was lost due to a database error:

"Alex Zhuravlev <bzzz@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/43989
Subject: LU-14825 lod: pool spilling
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 0a998f4723f58e68d0fe75934df5c282eb529337

Comment by Gerrit Updater [ 27/Sep/21 ]

"James Nunez <jnunez@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45056
Subject: LU-15011 tests: pool spill test modifications
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: a097f6ea7e5a9514c08995d6ed721cba05bb1fb0

Comment by Gerrit Updater [ 03/Oct/21 ]

"Alex Zhuravlev <bzzz@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45120
Subject: LU-15011 tests: ost-pools to remove big files
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: ad32cbc4f0654c3ae3c96b4bd1d1526445d94913

Comment by Gerrit Updater [ 10/Oct/21 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45056/
Subject: LU-15011 tests: pool spill test modifications
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: d8ff73097be78cc3e603ab49b6aaa03a1c766fcb

Comment by Gerrit Updater [ 17/Oct/21 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45120/
Subject: LU-15011 tests: ost-pools to remove big files
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: ebed0531abed9512682574e44dd17f465fa9b04c

Comment by Gerrit Updater [ 27/Oct/21 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/44947/
Subject: LU-15011 lod: count all spilling events
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 4bd9b524537bce27fb7f53cf481b78290cd55a1d

Comment by Gerrit Updater [ 08/Nov/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/45074/
Subject: LU-15011 tests: additional checks for pool spilling
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 26e765e0d23ba37577775331ac77ec857affd845

Comment by Cory Spitz [ 08/Aug/23 ]

Just curious, but was a LUDOC ever opened to track this Improvement?

Comment by Andreas Dilger [ 08/Aug/23 ]

spitzcor, I don't see it in the manual. However, I found your patch to add this documentation https://review.whamcloud.com/49725 "LUDOC-512 manual: add append_pool and append_stripe_count" and will land it now.

Comment by Andreas Dilger [ 08/Aug/23 ]

I filed LUDOC-517 for the "pool_spill" documentation.

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