vmallika at redhat.com
Fri Dec 18 09:00:39 UTC 2015
Here is the summary of discussion we had today on Quota-v2
Project, user and group quotas will use the same logic of accounting the
Quota-v2 should be compatible with both DHT-v1 and DHT-v2
Project quotas will use gfid of the given path as the project-id.
each inode will have a associated project-id which needs to be embedded
when creating new file, it will inherit project-id from its parent
In case if parent inode doesn't contain project-id, then there should
be a mechanism to
find the project-id given a gfid, so back-pointers can solve this
which xlator DHT/marker will set the project-id in the inode? this
needs to be decided
User and group quotas will use uid and gid to account the usage
Quota has below set of operation which should be performed as a single
read current size
read current contribution
update delta to the contribution
update size to user/project inode
In the current directory quota, to make this transaction crash consistent
we use a mechanism of setting dirty flag in a parent inode.
This mechanism will not work efficiently with project quotas. Journaling
will be the good solution for crash-consistency.
Quota 2 depends on:
back-pointers: to find project-id from gfid
journaling: for crash consistency of accounting
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel