[Gluster-devel] Object Quota feature proposal for GlusterFS-3.7
dlambrig at redhat.com
Tue Feb 24 17:35:41 UTC 2015
Not sure exactly what you are trying to do, but the changetimerecorder translator records in a database files that are created/modified/deleted/read (or some subset). This is a new translator thats part of the tier feature, though was written to be multipurpose and modular etc.
It uses the SQLlite database as a backend. You can put in a different backend. It does a lazy updates.
Feel free to take a look at it as well or inquire about it (Joseph authored this feature), just FYI.
----- Original Message -----
> From: "Vijay Bellur" <vbellur at redhat.com>
> To: "Prashanth Pai" <ppai at redhat.com>, "Luis Pabon" <lpabon at redhat.com>
> Cc: "gluster-devel at gluster.org >> Gluster Devel" <gluster-devel at gluster.org>
> Sent: Tuesday, February 24, 2015 2:11:07 AM
> Subject: Re: [Gluster-devel] Object Quota feature proposal for GlusterFS-3.7
> On 02/24/2015 10:54 AM, Prashanth Pai wrote:
> > Hi Luis,
> > Currently, even with storage policies, there is no mechanism to update the
> > container DBs with details of files created/modified/deleted over
> > filesystem interface.
> > Hence a GET on a container would list objects that may or may not exist on
> > disk. Also the metadata of container (bytes and object count) could be
> > outdated.
> > We need a mechanism to detect change in GlusterFS (have explored changelog
> > and inotify, both not feasible) and then lazily update Swift DBs so that
> > the container listing and metadata would eventually look right.
> What were the problems encountered while trying to use changelog?
> Gluster-devel mailing list
> Gluster-devel at gluster.org
More information about the Gluster-devel