<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">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).</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">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?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"> Venky</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 28, 2014 at 5:16 PM, Andrea Tartaglia <span dir="ltr"><<a href="mailto:me@andreatartaglia.com" target="_blank">me@andreatartaglia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">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. <br>
<br>
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. <br>
<br>
Thanks,<br>
<br>
<blockquote style="border:0px none" type="cite">
<div style="margin:30px 25px 10px 25px"><div style="display:table;width:100%;border-top:1px solid #edeef0;padding-top:5px"> <div style="display:table-cell;vertical-align:middle;padding-right:6px"><img src="cid:part1.04000003.03040404@andreatartaglia.com" name="149f638f53650615_postbox-contact.jpg" height="25px" width="25px"></div> <div style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a href="mailto:yknev.shankar@gmail.com" style="color:#737f92!important;padding-right:6px;font-weight:bold;text-decoration:none!important" target="_blank">Venky Shankar</a></div> <div style="display:table-cell;white-space:nowrap;vertical-align:middle">
<font color="#9FA2A5"><span style="padding-left:6px">13 November 2014
02:28</span></font></div></div></div><span class="">
<div style="color:#888888;margin-left:24px;margin-right:24px"><div dir="ltr"><div>It's
safe to purge everything under .processed. That what geo-rep had
already replicated, so it's OK to delete it.</div><div><br></div><div>Also,
consider purging these entries periodically as geo-rep doesn't purge
them on it's own (at least for now).</div><div><br></div><div>
Venky</div></div><div class="gmail_extra"><br><br></div>
</div>
</span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<div>-- <br>Andrea<br>
<br>
</div>
</font></span></div>
</blockquote></div><br></div></div>