Redis migration
Hi team,
I'm trying to migrate a V1 Redis to a V2 Redis database but I'm getting errors unfortunately. I've tried using the 1 Click migration which errored (screenshot) and I've tried separately adding a Redis database but nothing works in my existing Project – it simply doesn't deploy and no variables are added, and doesn't even produce errors, it is just empty. If I add a new Project, i'm able to add a V2 Redis database and finally I was shown what it looks like when it actually deploys and it's a big difference from what I'm seeing in the below Project ID.
This Redis migration is the first part in a migration to V2 for Redis and Postgres, then moving Regions. But I'm putting the brakes on until I can see a clear way forward.
Any help would be appreciated! 🙏
3e218ec0-7c31-4a5e-ba63-d0f7439aa07d
20 Replies
Project ID:
3e218ec0-7c31-4a5e-ba63-d0f7439aa07dWhat adding a new Redis database looks like in this Project
@jr - redis database migration failed
What adding a new Redis database looks like in a new Project
What it looks like now in my Project – I didn't add all these. It's Redis all the way down
Damn, that's a lot of databases
Sure is! So i'm trying to get a handle on all this before I look at Postgres which is far more critical
While you're in here team, I can't seem to add Volumes for whatever reason. As in, the UI doesn't exist. Oh wow – it hasn't been there for the last 30 minutes but it's just appeared 🤷♂️
(jr is the only team member in this thread)
I was shook when I found out (somehow?) that you weren't!
Hey @nickmacavoy,
We've pushed a fix that was failing the migration. Can you please try it again when you get a chance
Thanks – will do within the next hour
Project: 3c08e827-8d73-4a37-bbe9-9af9757bd354
Service: d67bde98-1985-42d1-b989-b60cc3dab69c
The service and its volume are in two separate regions. I want them both in Singapore. Why when I migrated from Oregon -> Singapore did it not migrate the data volume too?
Will address the Redis issue when I get a chance, there are levels of firefighting going on here
The two separate regions has happened with all services (PostGIS and Redis) i've migrated across to Singapore. All the data volumes remained in Oregon.
tagging back in @jr
Just fixing something related to that. Sorry it seems you caught a few bugs here. Can you switch them both back to USWest. I'll let you know when the fix is out and you can switch back to Signapore
I've resolved it. I removed the volumes and I re-added them which put them in the correct regions
I'm on a production app and i've had downtime
I'll do this for my staging environment when you give me the go-ahead
(yes I know, cart before horse!)
give the page a hard refresh and you should be good to go
Champion, thanks. ETA 60 mins
No rush
That worked thank you. Not within the same project, but I saw different behaviour when I tried on another
(by different I mean the correct behaviour)
Cancel that. I just tried migrating my PostgreSQL service to Singapore from Oregon on my staging project (3e218ec0-7c31-4a5e-ba63-d0f7439aa07d), and it migrated the service to Singapore but the data has remained in Oregon (volume 2aea168e-3d09-44be-ac33-05f9035046c8)
Hey, haven't forgotten about this. Will be taking a look first thing in the morning (est)
Just so you know, i've worked my way around it so it's not a blocker for me. My workaround was to move the service to Singapore, remove the volume still in Oregon, mount a new volume, profit
FYI my blocker is unrelated to this, #Client Error after Add Shared Variables . I pray nothing goes wrong while it's in this broken state and it has stopped me mid-migration until it's resolved