1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
So it looks like upgrading the cluster to 2.10.2
did indeed fix the issue, it just took some time for the dynamic resizing to finally kick in.
Over the course of the last 24 hours, it has gradually resized down to match the actual size of the database.
For anyone running into this in the future, upgrading your cluster engine and just... waiting seems to be the most appropriate course of action.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren