Timeline for MySQL Killed by OOM after Corrupted Database
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2016 at 15:45 | comment | added | Rick James |
table_open_cache may be too low, based on the very high Opened_tables. (Can't tell for sure without Uptime.)
|
|
| Apr 8, 2016 at 15:35 | comment | added | Rick James | add a couple of paragraphs about the QC | |
| Apr 8, 2016 at 15:35 | history | edited | Rick James | CC BY-SA 3.0 |
added a couple of paragraphs about the QC
|
| Apr 8, 2016 at 13:00 | comment | added | jkt123 |
Also, could you help me understand why a large query_cache_size would cause lengthy stalls? I thought that the query cache was to some degree for MyISAM what the buffer pool is for InnoDB.
|
|
| Apr 8, 2016 at 12:49 | comment | added | jkt123 |
No, I've never seen that many simultaneous connections, but I was maxing out with the default of 150. I did not raise tmp_table_size or max_heap_table_size. key_buffer_size is slightly bigger, but nowhere near 20% RAM. See my edited answer for variables and status.
|
|
| Apr 8, 2016 at 2:50 | history | answered | Rick James | CC BY-SA 3.0 |