Bug #102503 No locking happens using AutomaticThreadConfig
Submitted: 6 Feb 2021 18:18 Modified: 16 Nov 2021 20:38
Reporter: Mikael Ronström Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:8.0.23 OS:Ubuntu
Assigned to: CPU Architecture:Any

[6 Feb 2021 18:18] Mikael Ronström 
Description:
The code for AutomaticThreadConfig aims to lock the LDM thread and
Query thread to the same CPU core. However no threads are locked at all.

How to repeat:
Start with AutomaticThreadConfig and check output from node log.
No indication of CPU locking.

Suggested fix:
Ensure that threads in mt_thr_config.cpp sets m_bind_type.
[7 Feb 2021 9:09] MySQL Verification Team 
Hello Mikael,

Thank you for the report and feedback.

Sincerely,
Umesh
[16 Nov 2021 20:38] Jon Stephens 
Documented fix as follows in the NDB 8.0.28 changelog:

    When AutomaticThreadConfig was enabled, NumCPUs was always shown
    as 0 in the data node log. In addition, when this parameter is
    in use, thread CPU bindings are now made correctly, and the data
    node log shows the actual CPU binding for each thread.

Closed.