Hello there,
In the series of tests that I have been conducting one of them is related to failover with a multi region fdb.
Here is the configuration:
Configuration:
Redundancy mode - double
Storage engine - ssd-2
Log engine - ssd-2
Encryption at-rest - disabled
Coordinators - 9
Desired Commit Proxies - 3
Desired GRV Proxies - 5
Desired Resolvers - 2
Desired Logs - 3
Desired Remote Logs - 3
Desired Log Routers - 2
Usable Regions - 2
Regions:
Remote -
Datacenter - trt0
Satellite datacenters - trt4
Satellite Redundancy Mode - one_satellite_double
Satellite Logs - 2
Primary -
Datacenter - trt1
Satellite datacenters - trt5
Satellite Redundancy Mode - one_satellite_double
Satellite Logs - 2
Is the region of the datacenter trt0 I deleted the operator and then all the pod related to FDB which correctly led to a failover but I noticed that there was no datamovement after the fail over which is a sign that something is not going well.
And when I connected to a pod and ran fdbcli
I got
Warning: the database may have data loss and availability loss. Please restart following tlog interfaces, otherwise storage servers may never be able to catch up.
Old log epoch: 416 begin: 1469148180768 end: 1469914254878, missing log interfaces(id,address): 5ca7231f5aa0c2b1, 13a9b489bdb7574a, d5bf8a8d39512900,
This somewhat came as a surprise as we are supposed to have multi region with a primary and satellite so in theory anything committed to the primary should also be committed to the satellite and copied over when there is a failover but somehow it seems not to be the case ?
Is it a real issue ? also how do you map the id to pods or log server ?