Hi Dmitry

On Sat, Feb 20, 2021 at 6:24 AM Dmitry Yemanov <firebi...@yandex.ru> wrote:

> 20.02.2021 00:43, Lucas Schatz wrote:
> >
> > The async replication works correctly when both servers are running, the
> > journaling files are created and moved from log_directory to
> > log_archive_directory and the data is replicated almost instantly  to
> > the replica server. But when I stop the replica server and do some
> > operations on the primary server and restart the replica service then
> > the old pending data isn't replicated as I expected, but the new data
> > created after the restart is replicated correctly.
> >
> > This way I'm having an inconsistent replica, how can I fetch the pending
> > data to the replica?
> >
> > OS server: Centos8
> > Primary replication.conf:
> > database = /db/async.fdb
> > {
> >    sync_replica = SYSDBA:PASS@IP:/db/asyncreplica.fdb
> >     log_directory = /async/db1/chlog
> >     log_archive_directory = /async/db1/archlog
> >     log_archive_timeout = 10
> > }
>
> You have configured both synchronous and asynchronous replication. And
> the scenario you described is perfectly expected from a synchronous
> replication. You need to remove the "sync_replica" line.
>
> > Replica replication.log unchanged
>
> You probably meant replication.conf and if so this is your mistake. It
> should have something like this:
>
Yes, I mistyped it, sorry

database = /db/asyncreplica.fdb
> {
>    log_source_directory = /async/db1/archlog
>    verbose_logging = true
> }
>
> log_archive_directory at primary and log_source_directory at replica
> should be the same directory (or you should provide journal files
> copying from the primary side to the replica side).
>
>
So if I wan't to use async remotely, then I need to copy manually the files
from one server to another, correct?
Also, for the synchronous mode, I'm a little concerned about the fragility
in the sync state... is there a way to bypass the example that I did
without choosing async, for when the sync replica server is rebooted for
example but to to keep track of every passed operation when everything is
up again?

Thanks


> Dmitry
>
>
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to