Bug #47818 ndb_mgm reports "not connected" for ndbmtd nodes in phase 1 or phase2

• Submitted: 5 Oct 2:08
• Modified: 30 Oct 12:32
• Reporter: John David Duncan
• Status: Verified
• Category: Server: Cluster
• Severity: S3 (Non-critical)
• Version: mysql-5.1-telco-7.0
• OS: Any
• Tags: 7.0.7
• Triage: Triaged: D4 (Minor) / R6 (Needs Assessment) / E6 (Needs Assessment)

[5 Oct 2:08] John David Duncan

Description:
For some time during node restart -- some part of restart phases 1 and 2 -- an "all
status" command from ndb_mgm will falsely report "not connected" 

How to repeat:
Start a cluster and run "all status" repeatedly

[5 Oct 2:08] John David Duncan

sample screen capture during cluster restart

Attachment: mgm-status-bug.txt (text/plain), 6.46 KiB.

[30 Oct 12:32] Geert Vanderkelen

See also bug#48380 (which was marked duplicate of this bug report)

Quote from Cluster Development team, Magnus Blaudd:
"After fixing bug#48301, it should be possible to return CONNECTED(which is actually a
new status for API and MGM) when asking status for the ndbd.
I.e in the case when node is not connected to ClusterMgr with transporter yet but has
allocated node id."