Is anyone aware of whether the new compact -REPLICA command affects the replication history of an application?
Using this command to resolve ID table errors (Unable to extend an ID table - insufficient memory) seems like a promising solution, with some success being reported. However, when using the manual process to resolve this error (by creating a new replica from another location), it causes a loss of the replication history and forces a full replication for users. This can have a significant impact as this error occurs in very large databases, which results in huge network impacts after running.
I’d like to confirm whether this command affects/clears the replication history before I recommend its use for resolving this sort of error. Does someone have any experience around this?
Subject: compact - replica
This should nave no effct on the replication history for the file
Subject: Testing confirmed
Thanks for the responses. That is reassuring to hear.
I’ve managed to test on a large replica and confirm that the replication history is maintained, as such doesn’t require a one-time replication following completion.
Update - 30/10/2014
While initial testing showed that the replication history table was maintained, use of this command does force all users to do a full one-time only replication after the compact completes. This is something to be very wary of as the impacts for users can be significant for large databases with high document counts.
Subject: compact - replica
This should nave no effct on the replication history for the file
Subject: The history is preserved
Yes, the compact replica does propagate the history. This should allow continued use of the database without a performance hit once the compact is completed.