Run FoundationDB cluster on multi Kuberbetes clusters

[mason]

Thank a lots for your answer.

@johscheuer

That’s not possible writes will always go to the (active) primary region and has to be committed to the primary DC and the satellite DC. A read in theory can go to every region, with the limitation, that the GRV request will always be made to the primary DC and if a version is not available in the current (remote) region the read will be blocked until the version/mutation is available or a timeout is hit. So basically the setup of multi region in FDB is an active-passive model.

Maybe this is final question
Even I have multi_dc cluster, read/write request always comes to primary DC, is there anyway to improve read latency? I really want read request can read data at closest DC.