[LU-11571] MDT pool

• Type: Improvement
• Resolution: Unresolved
• Priority: Major
• Assignee: Peter Jones
• Reporter: CEA

Description

I brought the question up at JLUG2018, and cannot find any ticket for this; somewhere to discuss (and for others to show interest) might be good. Please mark as duplicate if I missed another one.

 

Basically, the way we're using DNE v1 right now is mostly to isolate populations: users we have little control over get their own MDT where if they cause problems only impact themselves, and the rest gets MDT0/other MDTs with hardcoded repartition.

 

With DoM we'll want to add more MDTs, yet still isolate populations. It would be good if we could shard/round-robin directory creations on a set of MDTs definted per directory.

 

One open question was "shall this be the same as the OST pool, or another one"?

For our use case, just adding the MDTs to the pool would work (we also separate populations per pool)

In the worst case if someone needs something independent they'd need to create a cross product of mdt/ost pools, which isn't great but could kind of work at small scale... I can't think of much usage to have these separately though. (I actually need to look at how PFL and pools interact, been out of touch; if we can have multiple pools set this way having a separate one for MDTs could just work?)

A simple rule of "no MDT set in the pool = any MDT" and similar for OST would probably be sound enough...

 

Any other open questions?

I'm not going to offer to look at the code for this yet, given how slow I am with the file create lock LU... Maybe once I'm done here and can free more time

 

Thanks!

Issue Links

• is related to: LU-15494 DNE3: "lfs setdirstripe -D" for specific MDTs
• is related to: LU-8616 DNE3: enhance "lfs mkdir" to select specific MDTs
• is related to: LU-17516 add 'lfs df --mdt' and 'lfs df --ost' options
• is related to: LU-13612 efficient DoM->OST component migration
• is related to: LU-11023 OST Pool Quotas