Inadequate default for thread_pool_max_threads

Bug #1258097 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Medium
Alexey Kopytov
5.5
Fix Released
Medium
Alexey Kopytov
5.6
Fix Released
Medium
Alexey Kopytov

Bug Description

The default value (500) for the thread_pool_max_threads variable is rather meaningless and provides an easy way for users to shoot themselves in the foot.

Limiting the total number of threads in the threadpool can result in deadlocks and uneven distribution of worker threads between thread groups in case of stalled connections.

Making it unlimited by default makes much more sense. This is to change both the maximum and default values for thread_pool_max_threads to 100k (the maximum max_connections value).

Related branches

description: updated
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1452

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.