Raised it on bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1169331
I'll keep track of it.
Thanks,
Andrea
Venky Shankar <mailto:[email protected]>
30 November 2014 01:43
The secondary node (passive replica) collects changelogs in
".processing" as the primary node (first replica) performs the
synchronization. On a replica failover, the passive replica (now
active) starts where the primary left. This _overload_ of changelog
backlog in the passive node is the cause of inode fill up (In primary,
changelog are moved to ".processed" which would still fill up inodes,
but I guess you purge them periodically now).
I guess you'd need to purge changlogs from ".processing" in the
secondary node, but the correct thing to do is to perform this
automatically in geo-replication. Could you raise a bug for this?
Venky
Andrea Tartaglia <mailto:[email protected]>
28 November 2014 11:46
Hi, Incurred in this problem again. After purging the .processed
everything went ok for a while. But now the .processing directory is
filling up which is going to bring to the same issue.
After some further investigation I found that this is happening only
on the secondary node, the primary one cleans up everything from the
.processing as soon as the file gets synced.
Thanks,
Venky Shankar <mailto:[email protected]>
13 November 2014 02:28
It's safe to purge everything under .processed. That what geo-rep had
already replicated, so it's OK to delete it.
Also, consider purging these entries periodically as geo-rep doesn't
purge them on it's own (at least for now).
Venky
--
Andrea
_______________________________________________
Gluster-devel mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
