vmallika at redhat.com
Mon Dec 21 05:57:55 UTC 2015
On Mon, Dec 21, 2015 at 9:43 AM, Nagaprasad Sathyanarayana <
nsathyan at redhat.com> wrote:
> Not clear as to why quota 2 must support both DHT v1 and v2. If customers
> continue to use dht v1, can we not allow them to use quota 1? We need not
> actively maintain quota v1 but only do reactive fixes.
> Idea is to have project quota in the early release and DHT-2 may not be
fully ready in the first release. so it is good to support DHT1 with
quota-2 till DHT-2 is stable.
> > On Dec 18, 2015, at 2:30 PM, Vijaikumar Mallikarjuna <
> vmallika at redhat.com> wrote:
> > Hi All,
> > 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 within inode.
> > 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
> > Thanks,
> > Vijay
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel