Bug #7153 Cluster nodes don't report error on endianness mismatch
Submitted: 10 Dec 2004 3:23 Modified: 10 Dec 2004 3:24
Reporter: Stewart Smith Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1 OS:Linux (Linux)
Assigned to: Stewart Smith CPU Architecture:Any

[10 Dec 2004 3:23] Stewart Smith
Cluster nodes in the same cluster cannot (yet) be of different endianness. In the event that a node is communicating with an ndb_mgmd of a different endianness, it should refuse to start and report an error. Currently it just sat there and did nothing.

How to repeat:
Try having a ndbd (on x86) communicate with ndb_mgmd, ndbd etc (on ppc).

Suggested fix:
bk commit - 4.1 tree (stewart:1.2126)
bk commit - 4.1 tree (stewart:1.2127)

these have been pushed.
[10 Dec 2004 3:24] Stewart Smith
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at