1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Youd want to review your Aurora logs for this period.
There may have been a case of a particular process or query that has been running and generating lots of log events in turn causing the storage to grow until it was restarted and the process cleared down.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Yes, that's what I think of too. But Aurora logging is turned off by default, isn't it. There is no logs information on Logs & events tab. We do logging lambdas, but I assume it shouldn't be taking in consideration since their logging is written into console not DB. Additionally log rotation should cut all the exceeded data by now. "When FILE logging is enabled, general log and slow query log files are examined every hour and log files more than 24 hours old are deleted. In some cases, the remaining combined log file size after the deletion might exceed the threshold of 15 percent of a DB instance's local space. In these cases, the oldest log files are deleted until the log file size no longer exceeds the threshold"