Bug #16197 ndb_mgm will now show when ndbd's have started
Submitted: 4 Jan 2006 17:49 Modified: 28 Feb 2006 19:12
Reporter: Jonathan Miller
Status: Closed
Category:Server: Docs Severity:S3 (Non-critical)
Version:5.1.5-alpha OS:Linux (Linux)
Assigned to: Jon Stephens Target Version:
Triage: D4 (Minor)

[4 Jan 2006 17:49] Jonathan Miller 
Description:
If the "all status" is done to quickly it can return dual results

ndbdev@ndb08:/space/run> ndb_mgm $ndbc -e "all status"
Connected to Management Server at: ndb08:14000
Node 4: starting (Phase 2) (Version 5.1.5)
Node 5: starting (Phase 2) (Version 5.1.5)

ndbdev@ndb08:/space/run> ndb_mgm $ndbc -e "all status"
Connected to Management Server at: ndb08:14000
Node 4: starting (Phase 2) (Version 5.1.5)
Node 5: starting (Phase 2) (Version 5.1.5)

ndbdev@ndb08:/space/run> ndb_mgm $ndbc -e "all status"
Connected to Management Server at: ndb08:14000
Node 4: Started (version 5.1.5)
Node 5: Started (version 5.1.5)
Node 4: starting (Phase 4) (Version 5.1.5)
Node 5: starting (Phase 4) (Version 5.1.5)

How to repeat:
see above

Suggested fix:
"all status" should never return dual results
[6 Feb 2006 15:27] Tomas Ulin 
ndb_mgm will report that nodes have started irrespective of a command given or not.

it is not the "all status" command giving "dual results".

the "node 4: Started" will always come out
[7 Feb 2006 0:59] Mike Hillyer 
Documenting status is only to flag that a bugfix needs a changelog entry, changing to
Verified.
[7 Feb 2006 11:14] Jon Stephens 
Um, no.

"Documenting" means this needs to be documented. 

Since this is a bug against the docs, there's no changelog entry to be made. That doesn't
alter the fact that it needs to be documented, hence Status should be "Documenting".
[8 Feb 2006 8:30] Jon Stephens 
Discussed with M Hillyer - setting category/status to Docs/Verified is the way to handle
these cases. My bad.
[17 Feb 2006 13:25] Jon Stephens 
What version(s) did this info start being reported? Thanks.
[23 Feb 2006 16:09] Tomas Ulin 
from 5.0.15
[28 Feb 2006 19:12] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

Documented feature change in 5.0.15 changelog. Closed.