I'm trying to set up asynchronous replication and, afaict, I have
followed all the steps in the release notes correctly. But replication
does not happen. Here is the config:
Primary:
database = /srv/data/active/ods130/bmsql_smoketest.fdb
{
log_directory = /var/fb4-replication/bmsql_smoketes
07.10.2019 13:24, Paul Reeves wrote:
Primary:
database = /srv/data/active/ods130/bmsql_smoketest.fdb
{
log_directory = /var/fb4-replication/bmsql_smoketest
log_archive_directory = /var/fb4-replication/archlog/bmsql_smoketest
log_archive_timeout = 10
verbose_logging = true
}
On Mon, 7 Oct 2019 16:30:00 +0300
Dmitry Yemanov wrote:
>
> verbose_logging is redundant here, currently it's used on the replica
> side only.
Thanks, I see now.
> > Replica:
> >
> > database = /srv/data/active/ods130/bmsql_smoketest.fdb
> > {
> >log_source_directory = /var/fb4-replicati
07.10.2019 17:00, Paul Reeves wrote:
Both servers are using Beta1
Upgrade to snapshot. It had been fixed since then.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On Mon, 7 Oct 2019 17:03:14 +0200
Dimitry Sibiryakov wrote:
> 07.10.2019 17:00, Paul Reeves wrote:
> > Both servers are using Beta1
>
>Upgrade to snapshot. It had been fixed since then.
>
>
Hmm - I thought of that, but couldn't see anything specific in the
commit log.
I'll try it.
Pau
Hi everybody
I'm testing the replication in Firebird4 RC1, and I'm experiencing a problem
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
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 ser
Hi Dmitry
On Sat, Feb 20, 2021 at 6:24 AM Dmitry Yemanov 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 rep
20.02.2021 19:20, Lucas Schatz wrote:
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 pas
Hello!
I was able do make async work
Thank you!
On Sat, Feb 20, 2021 at 5:07 PM Dimitry Sibiryakov wrote:
> 20.02.2021 19:20, Lucas Schatz wrote:
> > 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
New question:
async replication is working fine and created 5 chlog journal files
When I run rsync, Firebird successfully created/excluded everything, and I
noted that Firebird deletes the journal files... and created a "UUID
control file"
So, how I was curious I re-run a full rsync of the journal
21.02.2021 04:57, Lucas Schatz wrote:
async replication is working fine and created 5 chlog journal files
When I run rsync, Firebird successfully created/excluded everything, and
I noted that Firebird deletes the journal files... and created a "UUID
control file"
So, how I was curious I re-run
12 matches
Mail list logo
