readonly replica is returning data thats 5 hours old
we have a RW compute and RO compute. we are using nextjs + prisma deployed on vercel. noticed a few errors of records not being found. Narrowed it down to the RO replica not returning data we did a couple of checks and it was only returning data from 5 hours ago. our understanding is that it should read from the same source as the RW so there should be no lag?
we are using prismas extends ".$extends(
readReplicas({
url: process.env.RO_REPLICA,
})
);"
4 Replies
ugly-tan•2y ago
Hey JPG that sounds like an issue, can you open up a support ticket via the console so that our team can dig into it?
ratty-blushOP•17mo ago
Hi andy, we did create a ticket, I understand the team is looking into it but havent had an update yet. We currently switched off the prisma RO extension and doing everything through RW compute but hoping this is a short term fix until we can understand what happened and how we can monitor any lag in the future
eastern-cyan•17mo ago
There will be a slight lag, but it shouldn't be this long
ratty-blushOP•17mo ago
yes exactly, is there any monitoring tools available to measure or check the status of the RO vs RW? currently we are using the RW all connections while the RO is investigated, however we are looking to migrate a couple of projects that have 10x the volume or our current one and would need to understand more in depth what has happened and how can we mitigate it in the future