Bug #27644 ndb: connecting api node/mysqld may "steal" node_id from running mysqld

Submitted:	4 Apr 2007 12:30	Modified:	5 Apr 2007 9:31
Reporter:	Tomas Ulin	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
this can be seen causing failure of ndb_autodiscover3 on occasion

in this case the utility program ndb_desc connects to ndb_mgmd right after cluster comes up and receives the same node id as one of the mysqld's

How to repeat:
.

Suggested fix:
on disconnect the mysqld must disconnect completely and delete cluster connection, and recreate, to allocate new node id

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/23864

ChangeSet@1.2433, 2007-04-05 09:12:30+02:00, tomas@whalegate.ndb.mysql.com +1 -0
  Bug#27644 ndb: connecting api node/mysqld may "steal" node_id from running mysqld
  - test case workaround to avoid random failures

Pushed into 5.0.40

Pushed into 5.1.18-beta

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.