<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Thanks, Varun.<br></div><div><br></div><div>Please also fill out a page on the wiki using this template: <a href="http://www.gluster.org/community/documentation/index.php/Features/Feature_Template">http://www.gluster.org/community/documentation/index.php/Features/Feature_Template</a><br></div><div><br></div><div>And put the finished page in this directory: <a href="http://www.gluster.org/community/documentation/index.php/Features/<quota"><a href="http://www.gluster.org/community/documentation/index.php/Features/<ngquota_page>">http://www.gluster.org/community/documentation/index.php/Features/<ngquota_page></a></a><br></div><div><br></div><div>Thanks!<br></div><div><br></div><div>-JM<br></div><div><br></div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
<div class="moz-text-html" lang="x-western"> Hi Everyone, <br>
<br>
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. <br>
<br>
Current implementation <br>
* Client side implementation of quota <br>
- Not secure<br>
- Increased traffic in updating the ctx <br>
- Relying on xattrs updation through lookup calls <br>
* Problem with NFS mount <br>
- lack of lookups (handling through 'file handles') <br>
<br>
So, the new design is proposed,<br>
<br>
* Two level of quota implementation soft and hard quota, similar
to the XFS's quota, is introduced.<br>
A message is logged on reaching soft quota and no more writes
allowed after hard limit.<br>
<br>
* Quota is moved to server-side. <br>
Server side implementation removes the client dependability
for specific calls and secures the quota from mounting with
modified volfile.<br>
<br>
To get the cluster view,<br>
A trusted quota client process<b> </b>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.<br>
<br>
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.<br>
<br>
So, please share your opinion/suggestion/concerns about the above
draft.<br>
<br>
Thanks-to: Vijay, Amar, Raghavendra & Junaid.<br>
<br>
Regards<br>
Varun Shastry<br>
<br>
</div>
<br>_______________________________________________<br>Gluster-devel mailing list<br>Gluster-devel@nongnu.org<br>https://lists.nongnu.org/mailman/listinfo/gluster-devel<br></blockquote><div><br></div></div></body></html>