1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 2 ans