Bug #8645 Assertion failure with multiple management servers

• Submitted: 21 Feb 2005 13:00
• Modified: 25 Feb 2005 10:18
• Reporter: Hartmut Holzgraefe
• Status: Closed
• Category: Server: Cluster
• Severity: S3 (Non-critical)
• Version: 4.1.9
• Assigned to: Jonas Oreland

[21 Feb 2005 13:00] Hartmut Holzgraefe

Description:
When using a hostname as connect string i get the following assertion on starting 
the debug version of ndb_mgmd:

  ndb_mgmd: MgmtSrvr.cpp:2243: bool MgmtSrvr::alloc_node_id(NodeId*, ndb_mgm_node_type,
sockaddr*, socklen_t*, BaseString&): Assertion `*nodeId != 0' failed.

When giving a node ID as connect string instead all seems to be fine.

How to repeat:
See attached files

[21 Feb 2005 13:04] Hartmut Holzgraefe

Cluster configuration file with 2 management server nodes

Attachment: config.ini (application/octet-stream, text), 422 bytes.

[21 Feb 2005 13:05] Hartmut Holzgraefe

This connect string configuration leads to the assertion failure

Attachment: my.cnf (application/octet-stream, text), 286 bytes.

[21 Feb 2005 13:11] Hartmut Holzgraefe

just the nodeid alone doesn't work, too

Attachment: my.cnf (application/octet-stream, text), 280 bytes.

[21 Feb 2005 13:12] Hartmut Holzgraefe

with both node id and server name it works

Attachment: my.cnf (application/octet-stream, text), 304 bytes.

[21 Feb 2005 13:17] Hartmut Holzgraefe

Correction: assertion failure will only go away when specifying both node ID and host name