How long does database plugin migration take?
How much downtime should we expect?
14 Replies
Project ID:
N/AN/A
I tried this on a service that is no longer in use with a small postgres database and it locked up on the copy data stage. It's been almost 15 minutes now. Is this normal? I'm scared of letting my services go offline for 15+ minutes. Luckily this database is not in use, but that seems like a pretty long time to copy a 1mb database. My main app db is 30x the size at least.
Project id on this one: e1f04c05-5bea-4d11-b787-1f1e98108f2b
check the logs of the migration service please
It just popped off and finished. Took a pretty long time to migrate. However, this caused my n8n service to no longer work.
Is support for the old database plugin completely dropping on the 31st? Can we just continue to use it, while paying higher egress?
they will be deleted
that's an issue with the n8n template you deployed, the n8n template from jack works without issue
This is an older n8n template from about a year ago, but it is the one that was provided by Railway at that time. I have newer deployments of N8N using newer versions of the template, but I needed to test on this one, one that isn't used in anything mission-critical to see if it would work.
yeah then you shouldn't have to worry about this tini issue on your newer n8n deploys from the docker images
Can I send a few project IDs and get a verification that we will have a smooth migration? This is a very jarring conversion...
Project id 1: c437dc7f-ab9d-4f0a-8f63-ba05de523222
Project id 2: 34cc6607-4bf8-44c2-bed8-b7e4fbbe3386
I'm sorry I don't work for railway
No worries. Thank you for your help.
but as I understand it, the test migration you did, did work, just resulted in the unrelated n8n issue?
Looks like the data was migrated, yes. However, this server was responding before the migration and no longer responds after completing it.
Do you know if the credentials/host stay the same in this migration process? I have multiple apps tied into the different postgres databases, so I'm guessing they all need to be updated individually?
yes that's an unrelated issue with the old n8n template you used
host, port, username, password all change, but if you where using reference variables before all the variables should be updated seamlessly, if you where hardcoding your database credentials, it won't be seamless, and you will go need to replace the old database credentials with a reference to the new database's variables