7 days ago
On the Pro plan.
Multiple times, we've had Postgres DBs attached to volumes which have approached or hit their size limits. We receive alerts about these volumes nearing capacity and are instructed to resize the volume. For example, a volume was at 250GB, nearing capacity (~240GB full -- application stopped to avoid filling it).
When going to resize the volumes upon being alerted to do so, we have been blocked because the volume was not full enough. In the example above, the option to resize to 500GB was blocked because we needed to use at least 185GB of the volume's capacity.
We currently have a full volume blocking our application and cannot resize it, with the same sympoms. How do we fix this? How do we avoid this or manage this in the future?
3 Replies
Status changed to Awaiting Railway Response brody • 7 days ago
7 days ago
I have increased the volume to 500GB and will look into why the UI wasn't allowing a self-serve increase despite clearly meeting the threshold.
Status changed to Awaiting User Response Railway • 7 days ago
brody
I have increased the volume to 500GB and will look into why the UI wasn't allowing a self-serve increase despite clearly meeting the threshold.
7 days ago
That was fast. Thanks, brody. Yeah, just understanding this behavior would be helpful--even if it means that we need to be careful when we're growing databases because there is an X hour delay in the self-serve increase permission measurement. Or something like that.
Status changed to Awaiting Railway Response Railway • 7 days ago
7 days ago
It is unintended behavior; we had cached a zero value for the current volume size.
Going forward, for the gate check in the UI, we will fall back to the last nonzero value from the volume metrics, so this shouldn't be an issue going forward.
Status changed to Awaiting User Response Railway • 7 days ago