Prashanth , 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. Dan ----- Original Message ----- > From: "Vijay Bellur" <vbellur@xxxxxxxxxx> > To: "Prashanth Pai" <ppai@xxxxxxxxxx>, "Luis Pabon" <lpabon@xxxxxxxxxx> > Cc: "gluster-devel@xxxxxxxxxxx >> Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Tuesday, February 24, 2015 2:11:07 AM > Subject: Re: 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? > > Thanks, > Vijay > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
