Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
9223372036854775807
Description
We can also enforce a quota limitation of the capacity usage for each user, group, or project to provide cache isolation. An administrator can specify the quota enforcement on the local LPCC file system.
Thus, users can perform PCC-cached I/O on these files until they receive a return value -ENOSPC or -EDQUOT, which means that they hit the quota limit or that there is no free capacity left on the local PCC backend fs. At this time, I/O will fall back to the normal I/O path.
With this feature, it can have multiple PCC backends on a single client with different caching rules, so we can define upfront how much of the client FS can be used for each cache.
Attachments
Issue Links
- is duplicated by
-
LU-12356 Cache isolation via User/Group/Project quota on the PCC backend fs
- Resolved