> > > e.g. in A->B->C, when A fails to become B->C ? > > It is already B->C, there is nothing to do.
How about the case A->B->C, and B fails? Will A be replicating directly to C ? > Further, is it possible and how that from A->B->C the following happens > A<-B->C ? > > Switch A from primary mode to replica, switch B from replica mode to > master, > make corresponding changes in the configuration files, restart servers. > What does a switch from primary <-> replica mean? Only changing the configuration files? Restarting the servers: are there some performance issues expected due to restarting (looising data, long-time unavailability etc.) ? Am Mi., 27. Okt. 2021 um 14:14 Uhr schrieb Dimitry Sibiryakov < s...@ibphoenix.com>: > Pro Turm wrote 27.10.2021 13:52: > > Is it possible and how does a replica become primary at some point? > > As usual, changing of the replica mode of the database (if necessary at > all). > Read readme.replication.txt in doc folder. > > > e.g. in A->B->C, when A fails to become B->C ? > > It is already B->C, there is nothing to do. > > > Further, is it possible and how that from A->B->C the following happens > A<-B->C ? > > Switch A from primary mode to replica, switch B from replica mode to > master, > make corresponding changes in the configuration files, restart servers. > > The main problem is in database and application design that has to be > made > with replication in mind at the beginning. > > -- > 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
