achanda358
Joined 13 years ago
Joined 13 years ago
In my example, I will get a page for large replication lag. But not for an unplanned failover. That will be an alert, but not a page.
Why is this a problem? A typical deployment will have multiple replicas, with (hopefully) small replication lag. Those should be able to be promoted to be the new primary within a minute.
We are hiring a systems engineer at Cloudflare. Our team is responsible for managing all of Cloudflare's internal Postgres deployments. This particular role fullstack engineer-ish since this will involve writing frontend code for a system that engineers use to interact with databases, among other things. I am not the hiring manager but I am a part of this team, happy to answer any questions.
https://boards.greenhouse.io/cloudflare/jobs/5979113?gh_jid=...
my public key: https://keybase.io/achanda; my proof: https://keybase.io/achanda/sigs/zOV-L-Uspsh977GWKbT1Qy34C3AVTtkZh9d4BH7GVR8