Bug #55258 ndbd vanished after failed restart
Submitted: 14 Jul 2010 12:32
Reporter: Sveta Smirnova Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: CPU Architecture:Any

[14 Jul 2010 12:32] Sveta Smirnova 
Description:
32-bit ndbd vanished after I started it with data directory created by 64-bit ndbd

How to repeat:
1. Use 64-bit Cluster
2. Start 4 data nodes, management node and 2 SQL nodes
3. Created logfile group with undo file of 4G initial size, tablespace with 4 data files of 4G initial size
4. Create set of huge tables in this tablespace
5. Stop cluster
6. Compile 32-bit binaries from same source
7. Install
8. Start that 32-bit cluster
9. ndbd start will fail with " Node 2: Forced node shutdown completed. Occured during startphase 1. Initiated by signal 6. Caused by error 2353: 'Insufficent nodes for system restart(Restart error). Temporary error, restart node'." Error log contains error 1515: "NDB Error: Currently there is a 4G limit of one undo/data-file in 32-bit host [NDB Error Classification: SE (Schema error)] - MySQL Error Code: DMEC"
10. ls libexec directory of installation dir and you find no ndbd there.