ThreadPool does not print error messages even in case of critical problems

Bug #912611 reported by Elena Stepanova on 2012-01-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
Fix Released
Undecided
Vladislav Vaintroub

Bug Description

If something went really wrong with thread pool, e.g. it used up all threads (due to bad configuration) and further flow got locked up, we need to print meaningful error messages in the server error log. The messages should

- be real errors -- that is, not warnings, as warnings are often suppressed;
- be printed in a reasonable manner, without flooding the error log;
- identify problem as clearly as possible and maybe suggest further actions.

Additional warnings might also make sense, for example if thread pool approaches max_threads. Same requirements about not flooding the error log apply to them, too.

Elena Stepanova (elenst) wrote :

The bug is also filed in JIRA as MDEV-73

Changed in maria:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers