Bug #21320 2nd mysqld node fails to connect to cluster

• Submitted: 27 Jul 2006 19:24
• Modified: 17 Oct 2006 9:15
• Reporter: Nikolay Grishakin
• Status: Not a Bug
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 5.1
• OS: Linux (Linux)
• Assigned to: li zhou
• CPU Architecture: Any

[27 Jul 2006 19:24] Nikolay Grishakin

Description:
2nd mysqld node fails to connect to cluster when 2 mgm nodes are used in cluster.
Cluster consist of two hosts running ndb_mgmd and mysqld on each of them and two data nodes(hosts), two replicas. After we start two ndb_mgmd's, mysqld's on each manager host and start all data nodes second mysqld is not connected to cluster.
In order to get it connected we need to stop and start it again.

No errors reported in log files for mysqld on ndb17:

master1.err:
[ndbdev@ndb17 ngrishakin]$ cat /space/var/master1.err
060727 20:52:45  mysqld started
060727 20:52:55 [Note] Starting MySQL Cluster Binlog Thread
060727 20:52:55 [Note] /home/ndbdev/ngrishakin/builds/libexec/mysqld: ready for connections.
Version: '5.1.12-beta-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
060727 20:52:55 [Note] SCHEDULER: Manager thread booting
060727 20:52:55 [Note] SCHEDULER: Loaded 0 events
060727 20:52:55 [Note] SCHEDULER: Suspending operations

master1.log:
[ndbdev@ndb17 ngrishakin]$ cat /space/var/master1.log /home/ndbdev/ngrishakin/builds/libexec/mysqld, Version: 5.1.12-beta-log. started with:
Tcp port: 3306  Unix socket: /tmp/mysql.sock
Time                 Id Command    Argument

How to repeat:
See private section.