Resizing Volumes to 500GB (urgent)
aarongainz
PROOP

10 months ago

Hey team,

We started a migration from our MongoDB primary to 2 new secondary nodes.

We have a 500GB volume on the primary, but didn't realize this must've been a one-off. It's not allowing us to set our 2 new volumes to 500GB as well.

Can we get this updated fast? Sorry to be pushy - didn't think of this before we started this replication process.

Solved

31 Replies

10 months ago

I will escalate to the team


10 months ago

!t


10 months ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response medim 10 months ago


10 months ago

Can you share the link to those two volumes?


10 months ago

-# Beat me to it <:kek:1117578868140806164>



aarongainz
PROOP

10 months ago

Is there a way to enable our account to pick 500GB when we want?

Not a priority, just curious if this is possible as we build out more clusters.


irazvan2745
FREE

10 months ago

How do you have a mongodb that’s 500gb….


aarongainz
PROOP

10 months ago

this is a large production app


irazvan2745
FREE

10 months ago

Still…


irazvan2745
FREE

10 months ago

500gb for a single mongodb


irazvan2745
FREE

10 months ago

Is wild


10 months ago

People can operate large scale applications 🤷‍♂️


irazvan2745
FREE

10 months ago

Yeah but wouldn’t it be best if it’s split into multiple?


irazvan2745
FREE

10 months ago

Correct me if I’m wrong


10 months ago

Hence what the request of this is 😁


irazvan2745
FREE

10 months ago

I’m just curious <:idk:838948406990602291>


aarongainz
PROOP

10 months ago

well moving to multiple nodes is the first step for us, then eventually we're going to shard the db


aarongainz
PROOP

10 months ago

so effectively it will be "multiple" databases


10 months ago

Hello @aaron You would need to have an active deploy for us to increase the volume, can you please go ahead and start the services.


aarongainz
PROOP

10 months ago

doing that now - 1 min


aarongainz
PROOP

10 months ago

okay, we're online - let me know when this is done so I can kill the deployment and wipe volumes to restart replication


10 months ago

DB-1 now has a 500GB volume, but the backing store for DB-2 does not have enough space at this moment to accomdate a 500GB volume, I will have to raise this request to infra.


aarongainz
PROOP

10 months ago

i dont understand totally what this means - can you clarify my good sir


10 months ago

I cannot do 500GB for DB-2 myself; I will need to ask an infra engineer to do it for me.


aarongainz
PROOP

10 months ago

ahh right my bad, i appreciate your eyes on this.

any idea on ETA for this?


10 months ago

Should be within the next hour.


10 months ago

Our infra engineer is quite busy with a massive networking cutover right now; my previous ETA was not accurate.


aarongainz
PROOP

10 months ago

all good - looks like our data size is just under 250gb so we have a couple days of leeway here


10 months ago

Noted


10 months ago

Done, all 3 of the Mongo Databases are at 500GB now.

And I have a message from sales, they wanna talk to you now that you are growing on the platform! 🙂

Please do schedule a call!


10 months ago

!s


Status changed to Solved brody 10 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...