Hi,
I've got a bit of an unusual situation. I have two test servers that were configured
as a multi-master replication pair. One of the servers needed to be used for some separate
testing, which required disabling the replication. In the meantime, the second server has
been heavily used for regression tests.
Despite the replication agreements having been disabled for months now, the changelog on
the second server continues to grow. It has reached the point where the size has become
troublesome, but I am having trouble alleviating the situation.
I initially tried compacting the changelog, but that made no difference. I later noticed
using dbscan -f" that entries aren't being timed out from the changelog.
Essentially, it looks like entries are being added to the changelog as we do our periodic
regression tests; but since no replication session started, the changelog does not get
cleaned up.
I tried enabling the replication agreement while the first server was down, in the hopes
that the cleanup would be triggered. But, that did not work. Is there a way to force the
cleanup? Alternatively, since we don't care about the changes, can the changelog
safely be deleted?
Note, I'd prefer to not delete the replication agreement itself, but I would
appreciate a way to either prevent entries from being added into the changelog for now or
a way to ensure that the entries do not accumulate over time.
Thanks,
--
Iain Morgan
Show replies by date