gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Improvements in Quota Translator


From: Varun Shastry
Subject: Re: [Gluster-devel] Improvements in Quota Translator
Date: Wed, 10 Apr 2013 12:21:28 +0530
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5

John,

Sure, I'll do it once it is finalised.

Varun Shastry

On Tuesday 09 April 2013 07:16 PM, John Mark Walker wrote:
Thanks, Varun.

Please also fill out a page on the wiki using this template: http://www.gluster.org/community/documentation/index.php/Features/Feature_Template


Thanks!

-JM




Hi Everyone,

As gluster quota was facing some issues in its functionality, its required to make it fool-proof, robust and reliable. So, below are the some of the major problems we are facing and the modifications to overcome the same.

Current implementation
* Client side implementation of quota
    - Not secure
    - Increased traffic in updating the ctx
    - Relying on xattrs updation through lookup calls
* Problem with NFS mount
    - lack of lookups (handling through 'file handles')

So, the new design is proposed,

* Two level of quota implementation soft and hard quota, similar to the XFS's quota, is introduced.
    A message is logged on reaching soft quota and no more writes allowed after hard limit.

* Quota is moved to server-side.
    Server side implementation removes the client dependability for specific calls and secures the quota from mounting with modified volfile.

    To get the cluster view,
    A trusted quota client process will be spawned, on set of random 'n' bricks, containing only the cluster xlators, to aggregate the size on all the bricks of the volume. By querying for getxattrs on the directories, for a fixed time interval (say t secs), it updates the context of the quota xlator in server graph, by sending the setxattr with a key in dict. The t depends on lists, in the descending order for, 1. below soft limit 2. above soft limit; AND it is tunable.

    Thus in the current implementation we'll have 2 quota xlators: one in server graph, and one in trusted client of which the sole purpose will be to aggregate the quota xattrs on all the bricks and send the same to server quota xlator.

So, please share your opinion/suggestion/concerns about the above draft.

Thanks-to: Vijay, Amar, Raghavendra & Junaid.

Regards
Varun Shastry


_______________________________________________
Gluster-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/gluster-devel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]