Hi,
I had similar case.
One of our servers got out of disk space and not only replication
stopped, but the entries were removed from the _replicator DB.
The source of the problem was that someone started cleanup, when there
was not enough space, e.g. at least twice the size of the new, "clean" Db.
I had to manually re-create the replication definitions, once this was
done, things were Ok.
May be there is some sort of "expiration" setting and once this is hit,
the replication entry is removed?
------------------------------------------------------------------------
*With best regards,*
Kiril Stankov,
CEO
This Email disclaimer
<http://open-net.biz/emailsignature.html> is integral part
of this message.
On 2/9/2015 10:30 PM, Sinan Gabel wrote:
I have not tried it but I understand that coucdb will crash somehow if
there is not enough disk space during compaction.
But perhaps you should present some more facts about your installation and
environment and some of the gurus can help :)
On Monday, February 9, 2015, Bill Foshay <[email protected]> wrote:
Another thing you may want to check is that you have enough disk space
for
compaction. As I recall it needs at least 2x the size of the compacted db
size.
Does compaction affect continuous replications? Will it cause them to stop
or to be removed from the replicator database?
