[Gluster-devel] Geo-replication fills up inode by saving processed changelog files

Aravinda avishwan at redhat.com
Thu Dec 11 06:10:12 UTC 2014


Hi,


While geo-replication is running it keeps processed changelog files in 
$WORKING_DIR/.processed or $WORKING_DIR/.history/.processed. These 
changelog files are useful for debugging processed changelogs. But these 
changelogs eats up the space/available inodes. The changelog files saved 
in processed directory is duplicate of changelogs available in brick 
backend(Difference is in the format, changelogs in processed dir are 
parsed and human readable).

How about keeping only the reference to changelog file after processed. 
For debugging their will be additional step to look for changelog from 
backend($BRICK/.glusterfs/changelogs) using this reference.

After syncing data to slave(In geo-replication)
echo $changelog_filename >> $WORKING_DIR/.processed_files
rm $WORKING_DIR/.processing/$changelog_filename

We need to modify `gf_changelog_done` and `gf_history_changelog_done` 
functions in libgfchangelog($GLUSTER_SRC/xlators/features/changelog/lib/src)

Any thoughts?

--
regards
Aravinda


More information about the Gluster-devel mailing list