[Gluster-users] Scheduled AutoCommit Function for WORM Feature

Karthik Subrahmanya ksubrahm at redhat.com
Tue Feb 27 10:35:57 UTC 2018

Hi David,

Yes it is a good to have feature, but AFAIK it is currently not in the
priority/focus list.
If anyone from community is interested in implementing this, is most
Otherwise you need to wait for some more time until it comes to focus.

Thanks & Regards,

On Tue, Feb 27, 2018 at 3:52 PM, David Spisla <spisla80 at gmail.com> wrote:

> Hello Gluster Community,
> while reading that article:
> https://github.com/gluster/glusterfs-specs/blob/master/
> under_review/worm-compliance.md
> there seems to be an interesting feature planned for the WORM Xlator:
> *Scheduled Auto-commit*: Scan Triggered Using timeouts for untouched
> files. The next scheduled namespace scan will cause the transition. CTR DB
> via libgfdb can be used to find files that have not changed. This can be
> verified with stat of the file.
> Is this feature still in focus? It is very usefull I think. A client does
> not have to trigger a FOP to make a file WORM-Retained after the expiration
> of the autcommit-period.
> Regards
> David Spisla
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180227/de25ff7c/attachment.html>

More information about the Gluster-users mailing list