Bug #24445 MySQL Cluster Upgrade - Pointer too large - Error: 2306

Submitted: 20 Nov 2006 18:40 Modified: 20 Nov 2006 22:32
Reporter: Matthew Boehm Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.1.12-beta OS:Linux (RHEL4 - 2.6.9-42.0.3.ELsmp)
Assigned to: Jonas Oreland CPU Architecture:Any

[20 Nov 2006 18:40] Matthew Boehm
Description:
Upgrading mysql-cluster from 5.0.27 to 5.1.12-beta

3 server setup. ndb_mgm on A. mysqld and ndbd on B and C

Everything compiled fine. Installed fine. ndb_mgm running fine. mysqld's running fine.

All attempts to bring nodes online have resulted in the following:

ndb_mgm> Node 2: Forced node shutdown completed. Occured during startphase 1. Initiated by signal 0. Caused by error 2306: 'Pointer too large(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'.

Time: Monday 20 November 2006 - 18:15:21
Status: Temporary error, restart node
Message: Pointer too large (Internal error, programming error or missing error message, please report a bug)
Error: 2306
Error data: dbdih/DbdihMain.cpp
Error object: DBDIH (Line: 13385) 0x0000000a
Program: /usr/libexec/ndbd
Pid: 5966
Trace: /var/lib/mysql/ndb_2_trace.log.4
Version: Version 5.1.12 (beta)
***EOM***

How to repeat:
I went through a brand new make clean; make; make install and attempted to bring online again the nodes with same result.

Suggested fix:
Was able to get running again by doing --initial on the 2 nodes.
[20 Nov 2006 18:40] Matthew Boehm
trace mentioned in error

Attachment: ndb_2_trace.log.4.gz (application/gzip, text), 3.21 KiB.

[20 Nov 2006 22:32] Jonas Oreland
Hi,

We currently only support upgrade from 5.0 to 5.1 using either
  ndb_restore on mysqldump

Sorry about this :(

/Jonas

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.