a year ago
(My work email, which is on Pro plan, is not the same as the one I'm using on Discord.)
Title is self explanatory. When I change the region from Metal US East to Metal US West, the service immediately triggers a deployment without trying to actually migrate the attached volume first. The volume stays in US East, while the service gets deployed to US West, which throws an error during the deployment phase.
Postgres has kind of been a pain in the ass lately. Failed/delayed deployments, enormous IO write delays, etc. What gives?
c6475270-9fec-46fc-a7a1-294095b6469c
6 Replies
a year ago
Hello,
What environment should I be looking at?
a year ago
Both the service and the volume are located in US-East, may I try triggering a migration to US West?
The volume migration appears to be working this morning. I had to migrate the service back to East yesterday because this is a production environment.
a year ago
!s
Status changed to Solved brody • 11 months ago