- Newest
- Most votes
- Most comments
Bump. I have just pulled 1.7MB mysql-error-running.log and it is 3500 lines with just this text in each line...
Exactly the same thing happening here on a db.t3.small. Can't find any information anywhere to explain what it might be.
Check your freeable memory stats. I think this is an OOM (Out of memory) error
Did anyone find a solution for this?
Also seeing this with db.t3.small . Not yet find the right way to reduce memory in a way that fixes this.
Hello, I was having the same issue with a mysql db.t3.small database. I was using a pooled connection with 20 concurrent connections which was taking to much memory. I was also having some oom and some login failures when the OOM was happening. By lowering to 10 concurrent connections, the issue is fixed. Hope it helps :)
Im also using db.t3.small for my dev environment, on mysql engine starts I see warning about memory is low, before establishing any connections. The db is still working fine thou.
[Note] /rdsdbbin/oscar/bin/mysqld: ready for connections.
Version: '5.7.12' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
Available memory is low. Trying to avoid OOM crash: system KB: 1970520 available KB: 80036 low-threshold KB: 98526 print victim: yes decline query: no tune caches: yes kill query: no kill connection: no
(oscar_oom.cc:1210)
(oscar_oom.cc:1210)
(oscar_oom.cc:1210)
....
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated 10 months ago
