> > > How about the case A->B->C, and B fails? Will A be replicating directly > to C ?
And how about the following constellation: A->B->C .......|->D .......|->F i.e. B was originally replicating to C, D, F simultaneously, before it failed. How could the replication from A to C, D, F simultaneously be restored, i.e. is there any performance or other issues compared to the case A->(B)->C ? Am Mi., 27. Okt. 2021 um 14:39 Uhr schrieb Pro Turm <protu...@gmail.com>: > > How about the case A->B->C, and B fails? Will A be replicating directly >> to C ? >> >> No. >> > Which means cascading could be quite vulnerable. What is then the quickest > possible way to connect A to C in the above case? > > > Restarting the servers: are there some performance issues expected due >> to >> > restarting (looising data, long-time unavailability etc.) ? >> >> It depends. >> > Could you please elaborate more on that ? > > Am Mi., 27. Okt. 2021 um 14:33 Uhr schrieb Dimitry Sibiryakov < > s...@ibphoenix.com>: > >> Pro Turm wrote 27.10.2021 14:26: >> > How about the case A->B->C, and B fails? Will A be replicating >> directly to C ? >> >> No. >> >> > What does a switch from primary <-> replica mean? Only changing the >> > configuration files? >> >> No, it is invoking "gfix" command with appropriate switches as >> described in >> README.replication.txt. >> >> > Restarting the servers: are there some performance issues expected due >> to >> > restarting (looising data, long-time unavailability etc.) ? >> >> It depends. >> >> -- >> WBR, SD. >> >> >> 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
