> 1. Depend on change-log to recompute checksum. This eliminates
> periodic crawl of brick/volume to update the checksum.
>
Consumption would be very much similar to how Geo-replication makes use of
journals, i.e. notification after a specified time interval. If you need
somewhat realtime notifications, that can be worked upon. For already
existing data on a volume you could fallback to a FS crawl and use
changelog thereafter.
FWIW, an history API for changelog consumption (from bricks) would be of
much use here (given a [start-time, end-time], fetch all changelogs given
that change-logging was _always_ enabled in that time duration, else resort
to FS crawl).
Venky
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
