ArangoDB 2.8.2 maintenance release comes with several replication improvements and bug fixes. You can download the latest version from our download page.
the continuous replication applier will now prevent the master’s WAL logfiles from being removed if they are still needed by the applier on the slave. This should help slaves that suffered from masters garbage collection WAL logfiles which would have been needed by the slave later.
The initial synchronization will block removal of still needed WAL logfiles on the master for 10 minutes initially, and will extend this period when further requests are made to the master. Initial synchronization hands over its handle for blocking logfile removal to the continuous replication when started via the
setupReplicationfunction. In this case, continuous replication will extend the logfile removal blocking period for the required WAL logfiles when the slave makes additional requests.
All handles that block logfile removal will time out automatically after at most 5 minutes should a master not be contacted by the slave anymore (e.g. in case the slave’s replication is turned off, the slaves loses the connection to the master or the slave goes down).
added all-in-one function
setupReplicationto synchronize data from master to slave and start the continuous replication:12require("@arangodb/replication").setupReplication(configuration);
The command will return when the initial synchronization is finished and the continuous replication has been started, or in case the initial synchronization has failed. More