Hi Pieter, On Mon, Nov 27, 2017 at 09:43:52PM +0100, PiBa-NL wrote: > Hi List, > > I thought i 'reasonably' tested some of 1.8.0's options. > Today i put it into 'production' on my secondary cluster node and notice it > takes 100% cpu...
Grrrr.. bad. This sounds like another case of recursive locking. > I guess i should have tried such a thing last week. Don't worry, whatever the amount of tests you run, some bugs will always slip through. > Anyhow below some gdb and console output. Very useful, I found it : process_chk_conn() takes the lock then calls connect_conn_chk() : 2114 HA_SPIN_LOCK(SERVER_LOCK, &check->server->lock); 2137 ret = connect_conn_chk(t); connect_conn_chk() then calls tcpcheck_main() : 1548 tcpcheck_main(check); And this one takes the lock again : 2598 HA_SPIN_LOCK(SERVER_LOCK, &check->server->lock); CCing Emeric as he's the one who covered the checks so he will know best how to fix it. In the mean time, if you don't need threads you can rebuild with "USE_THREAD=" to disable them, but I'd rather wait for a fix. Sorry about that, and thaks for the report. Willy
