dflt_key_cache->key_cache_mem_size is not set, signal hanlder prints key_buffer_size=0 in the error log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
Medium
|
Igor Babaev |
Bug Description
When server gets a signal which causes an abort and attempts to print some debug info in the error log, key_buffer_size is displayed equal 0. It seems to be always so in MariaDB 5.2, 5.3, 5.5, while in MariaDB 5.1, MySQL 5.1 and 5.5 the real value is printed.
From what I could see from a quick look, the printed value is dflt_key_
I'm not sure how much the variable is used later, so it might be only a cosmetic problem (bad error message), or a functional issue if some other code relies on the value.
To reproduce the visible effect, start mysqld, let it start up properly, then kill it with SIGABRT or alike and see the error output:
We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.
key_buffer_size=0
read_buffer_
max_used_
max_threads=153
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
summary: |
- dflt_key_cache->key_cache_mem_size is not set, signal hanlder - printskey_buffer_size=0 in the error log + dflt_key_cache->key_cache_mem_size is not set, signal hanlder prints + key_buffer_size=0 in the error log |
description: | updated |
Changed in maria: | |
assignee: | nobody → Igor Babaev (igorb-seattle) |
Changed in maria: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in maria: | |
status: | Confirmed → In Progress |
Changed in maria: | |
status: | In Progress → Fix Committed |
Changed in maria: | |
status: | Fix Committed → Fix Released |