Bug #55383 Table ndbinfo.config_params should be read-only (for now)
Submitted: 19 Jul 2010 21:26 Modified: 12 May 2015 16:43
Reporter: Joffrey MICHAIE Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.1 OS:Linux
Assigned to: CPU Architecture:Any
Tags: 7.1.3, 7.1.4b, cluster, config_params, ndb, ndbinfo

[19 Jul 2010 21:26] Joffrey MICHAIE
Description:
Hello,

It is currently possible to change the "ids" of the parameters in the ndbinfo.config_params table !

This is an issue, because I don't think we want these param_number to be changed on the fly, and probably some users may think that changing it will in fact change the parameter ....

 

How to repeat:
Run a Cluster with default configuration :

mysql> select * from config_params where param_name=  'TransactionDeadlockDetectionTimeout';

+--------------+-------------------------------------+

| param_number | param_name                          |

+--------------+-------------------------------------+

|          131 | TransactionDeadlockDetectionTimeout |

+--------------+-------------------------------------+

1 row in set (0.00 sec)
 
mysql> update config_params set param_number=1200 where param_name='TransactionDeadlockDetectionTimeout';

Query OK, 1 row affected (0.00 sec)

Rows matched: 1  Changed: 1  Warnings: 0

 

mysql> select * from config_params where param_name  ='TransactionDeadlockDetectionTimeout';

+--------------+-------------------------------------+

| param_number | param_name                          |

+--------------+-------------------------------------+

|         1200 | TransactionDeadlockDetectionTimeout |

+--------------+-------------------------------------+

1 row in set (0.00 sec)

(And reverse change it ..)

 

Suggested fix:
Make this table r/o 
or
Add capability to change the setting with a 3rd column :)
[19 Jul 2010 22:02] Sveta Smirnova
Thank you for the report.

Verified as described.
[12 May 2015 16:43] Jon Stephens
Fixed in NDB 7.5. Documented in the NDB 7.5.0 changelog, as follows:

        The ndbinfo.params table is now read-only.
      
Closed.