Bug #34394 thread_pool_size system variable should not be dynamic
Submitted: 7 Feb 2008 20:08 Modified: 19 May 2010 0:17
Reporter: Paul DuBois Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:6.0 OS:Any
Assigned to: CPU Architecture:Any

[7 Feb 2008 20:08] Paul DuBois
Description:
Per the discussion below, the thread_pool_size system variable currently is dynamic, but should not be. It should be settable only at server startup.

At 9:32 PM +0200 2/7/08, Michael Widenius wrote:
Hi!

>>>>> "Paul" == Paul DuBois <paul@mysql.com> writes:

Paul> I'm going to take issue with one of Monty's statements. :-)
Paul> At 11:22 PM +0200 2/1/08, Michael Widenius wrote:
>> Hi!
>> 
>>>>>>> "Konstantin" == Konstantin Osipov <konstantin@mysql.com> writes:
>> 
>> <cut>

>> >> The thread_pool_size system variable can be set at runtime (is
>>>> dynamic)?
>> 
Konstantin> Don't know.
>> 
>> No, it can't be set at runtime (All the worker threads are started
>> when mysqld starts).

Paul> That seems not to be true:

mysql> select @@global.thread_pool_size;
Paul> +---------------------------+
Paul> | @@global.thread_pool_size |
Paul> +---------------------------+
Paul> |                        20 |
Paul> +---------------------------+
Paul> 1 row in set (0.00 sec)

mysql> set @@global.thread_pool_size = @@global.thread_pool_size + 1;
Paul> Query OK, 0 rows affected (0.00 sec)

mysql> select @@global.thread_pool_size;
Paul> +---------------------------+
Paul> | @@global.thread_pool_size |
Paul> +---------------------------+
Paul> |                        21 |
Paul> +---------------------------+
Paul> 1 row in set (0.00 sec)

Paul> So it *is* dynamic.  The question then becomes, is it *supposed*
Paul> to be dynamic, or is it a bug that this variable can be set at runtime?

It's a bug that this can be set runtime.

Regards,
Monty

How to repeat:
N/A
[7 Feb 2008 20:14] MySQL Verification Team
Thank you for the bug report.
[19 May 2010 0:18] Paul DuBois
This variable was removed in 6.0.14. No longer anything to fix.