My db.t2.micro is stuck "in progress" after storage size modification

0

My PostgreSQL db running on a db.t2.micro RDS ran out of storage (Status: Storage-full) and I've lost all connection to it.

I tried modifying it to increase the storage to 20GB, but it's been "in progress" for the last 11 hours with no indication that it will ever complete.

I'm a bit concerned that in the "Maintenance & backups" tab, it has a section for Maintenance that it implies a "Pending modifications - Allocated storage: 20 GiB" happening in a maintenance window in 5 days time. I remember using "apply immediately".

I've also noticed that "Current Region backups" shows a spinner which fails to ever load anything.

The closest info I can find on my situation is this: https://aws.amazon.com/premiumsupport/knowledge-center/rds-stuck-modifying/ but I'm not sure how I can practically action the suggestions given the current state of the rds.

I can't take a snapshot while the database in is this "in-progress" state.

Is there a way to increase the storage in a timely manner, and in such a way that I know when it will be completed?

[edit] After looking back through my logs, I have this error

psycopg2.errors.DiskFull: could not write to file "pg_wal/xlogtemp.8331": No space left on device

which seems related to this article: https://aws.amazon.com/premiumsupport/knowledge-center/diskfull-error-rds-postgresql/ although trying to connect to the device is an issue, at least from a client app running on my desktop.

gmcc051
asked 2 years ago330 views
1 Answer
0

That spinner behaviour on "Current Region backups" indicates you're missing some permission. I'd resolve this forst so you know you're getting true up-to-date info in the console, then see how your db looks.

Though it's odd you've lost connection to the db - it should be available for reads and writes when adding storage thoughyou may experience degraded performance until the process is complete. Adding storage may take several hours.

EXPERT
answered 2 years ago
  • I edited the initial post stating the original diskfull error.

    If I try to connect via psql, I get

    psql: error: connection to server at "<my db endpoint>, port 5432 failed: Connection refused
    	Is the server running on that host and accepting TCP/IP connections?
    

    And that despite the db being "Publicly accessible" and having inbound/outbound rules allowing 0.0.0.0/0 port 5432

  • In https://aws.amazon.com/premiumsupport/knowledge-center/rds-out-of-storage/#:~:text=An%20Amazon%20RDS%20DB%20instance,storage%20of%20your%20DB%20instance. it says "An Amazon RDS DB instance in the storage-full status doesn't have enough available space to perform basic operations, such as connecting to or restarting the instance.". It accepts only allocated storage modifications. Any modifications for other values are rejected. You must increase allocated storage by at least 10%. An increase less of than 10% results in an error.

  • Under the maintenance tab, it's listed "Pending modifications - Allocated storage: 20 GiB", but it has been like that for about 36 hours. This was after my attempt to increase the size from 5GB to 20GB. I have no idea why "apply immediately" had no affect because from the information in the maintenance tab, it seems to imply that this modification won't happen until the 25th (a maintenance window?). Thankfully I had a backup and was able to create a new database, but for curiosity, I'll wait till the 25th to see if the modification eventuates.

  • It took 4 days, but the resize finally happened and Maintenance: in-progress has changed to available. I've since moved to a different db.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions