| Bug #116351 | Error assigning node ID during synchronization of mysql NDB cluster | ||
|---|---|---|---|
| Submitted: | 14 Oct 2024 1:22 | Modified: | 18 Dec 2024 14:53 |
| Reporter: | CunDi Fang | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 8.0.35-cluster MySQL Cluster Community S | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[14 Oct 2024 1:22]
CunDi Fang
[14 Oct 2024 5:27]
MySQL Verification Team
Hi, Please upload full ndb_error_report and all the logs from SQL nodes. Thanks
[16 Oct 2024 4:13]
MySQL Verification Team
Please attach the zip with *all* log files. Use ndb_error_reporter script https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-programs-ndb-error-reporter.html
[16 Oct 2024 7:34]
MySQL Verification Team
Great, thanks. Is this the same setup on improperly configured docker? It might be the same issue too. If it is, can you retest with properly configured docker?
[16 Oct 2024 8:12]
CunDi Fang
Yes, this is same with 116349, I did not set the CAP_SYS_NICE:
```
"HostConfig": {
"Binds": null,
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "mysqlcluster_net2",
"PortBindings": {},
"RestartPolicy": {
"Name": "no",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null, //HERE
"CapDrop": null,
"CgroupnsMode": "private",
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
```
Since I only keep log files, it's also difficult for me to reproduce a time series of strictly one. But I can confirm that I'm not involving thread allocation or Resource Groups or anything like that. I'm just interacting normally, so it's logical that this configuration item shouldn't affect it, right?
[18 Dec 2024 14:53]
Jon Stephens
Documented fix as follows in the NDB 8.0.41, 8.4.4, and 9.2.0 changelogs:
Errors of unknown provenance were logged while assigning node
IDs during cluster synchronization, leading to user doubt and
concern. Logging of the data node QMGR block and the ndb_mgmd
process relating to node ID allocation issues has therefore been
improved, to supply more information about what is being reported
in such cases.
Closed.
