Bug #52566 | ndbinfo.transporters vs. docs when remote_node_id is not connected | ||
---|---|---|---|
Submitted: | 2 Apr 2010 23:34 | Modified: | 4 May 2014 6:45 |
Reporter: | John David Duncan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Documentation | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.1 | OS: | Any (Mac OS X 10.5, Linux) |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
Tags: | 7.1.3, ndbinfo |
[2 Apr 2010 23:34]
John David Duncan
[3 Apr 2010 9:37]
Sveta Smirnova
Thank you for the report. Verified as described.
[3 Apr 2014 12:24]
Magnus BlÄudd
Posted by developer: This bug is regarding the state of transporter connections vs how those are documented in the manual. > (1) The transporter is actually listening for a new connection, CONNECTING is > the correct state, and the docs are wrong. ^ Yes, the transporters will always go back to state CONNECTING as soon as the disconnect of the old node has completed. Solution: The documentation should be updated to reflect that CONNECTING is the normal state for connections to node which are not started. Note! The output also shows(peculiar) connection to own node, i.e 1<->1 or 2<->2 which is always DISCONNECTED. If that is annoying please file new bug asking for own node connections to be removed from the output. Should be filtered inside the ndbd.
[5 May 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".