You will see metrics for each region
You will see metrics for each region serving queries, yes. But, replicas are used only on-demand for queries inside each region, they don't run all the time. For example, if you have traffic in ENAM and EEUR, you should see the primary and the replicas in those two regions being in your metrics.
5 Replies
ok, my primary is in ENAM but i'm in the UK "testing" but absolutly nothing is showing for EEUR, Uk etc. This does work with "workers" smart placement as wel doesnt it?. I'm hitting the worker, the queries are in the worker, worker shows UK traffic, binding to D1 in worker
Can you share your DB ID and account ID with me (send DM) to check that read replication is enabled?
You can try disabling and re-enabling it, just to see if that helps in the meantime until I have the IDs to check our logs.
Keep in mind as well that you have to use the Sessions API for replicas to be used, and also send a couple requests so that the replica manages to boot before start serving your queries. During boot queries are forwarded to the primary.
Just to close the loop on this for others, this hit an edge case that even though the control plane thought it enabled read replication, it actually didn't reach the database so read replication was not enabled.
We are reviewing the fix for this as we speak, and I will post in the channel once the fix is rolled out.
Apologies for the confusion.
@lambrospetrou any word of a fix here yet?
A fix is out already since last Friday. If you disable and re-enable replicas in the UI or REST API, it should work now. If not, then there is some other issue that we would have to look into.
I didn't post anything here cause I wanted to first release another change to automatically "fix" databases that hit this edge case.
Feel free to test it out and let me know if you still don't see replicas created after some requests to allow the replica to boot.
ok, i see some regions starting to appear, so seems to be working now