From: Krzysztof B. <kb...@un...> - 2017-07-04 14:41:46
|
Hi Sander, W dniu 04.07.2017 o 15:28, Sander Apweiler pisze: > Hi Krzysztof, > > today we had some problems with SQL Session. The logfile output is > appended below. Nothing in logfile indicates a reason for this problem. > DB log shows no problem/error. One SQL session was kept for 1129 > seconds. Parallel to this warnings the CPU usage increased to 100%. > During the problem was a training course where 40 users created new > accounts and/or singed in. > > We use a mariadb on the same host. It was the first time we had this > problems. Do you have a hint when this error is shown in the log files? Nothing to worry about. This is an internal watchdog that suspicious transactions - those which take long to complete. Threshold (quite arbitrary) is set to >3s. If this happened during a peak load - then no problem. If this happens during regular operation, may mean that we have a bug/deadlock and then this stack trace is very valuable. Best Krzysztof |