Migration plan feedback

5 comments · 4 participants

Priya NandakumarPlatform · 2h ago

The cutover window is tight. If we hold the read replica until the backfill drains we lose the rollback path, so I would rather split this into two deploys.

Marcus Bell1h ago

Agreed. Two deploys also means the schema change lands on a quiet day instead of during the migration itself.

Sofia Alvarez48m ago

I can prepare the second deploy behind a flag so we can flip it without another release.

Wei ChenData · 36m ago

One caveat: the backfill job reads from the same connection pool as the API. We should cap it at eight workers or the request latency will spike during business hours.

Tomás GuerreroReliability · 12m ago

Added a dashboard for pool saturation so we can watch it live. Alert fires at 80 percent for five minutes.

Mention a teammate with @ to notify them.