I am attempting to load ~3,000,000 records into table using a LOAD DATA statement. Record size is 48 bytes, 32 byte primary key, and an additional non-unique ordered index. ~19,000 records are loaded then I get a node failure. The error in the log file is: Date/Time: Tuesday 16 November 2004 - 12:09:51 Type of error: error Message: Pointer too large Fault ID: 2306 Problem data: DblqhMain.cpp Object of reference: DBLQH (Line: 12820) 0x0000000a ProgramName: NDB Kernel ProcessID: 15609 TraceFile: /usr/local/mysql-cluster/ndb_2_trace.log.11 ***EOM***

What does the error "Pointer too large" mean?

After the node failure, I restart the cluster nodes, and the MYSQLD nodes will not reconnect right away, takes 5-10 minutes. What is the reason for the delay? Is there a way to force mysqld to reconnect to the mgmd [a mysqld restart doesn't do it]?

I am running the MySQL-Max v4.1.7 cluster on 2 Linux machines with 1 replica. Here's my config: [COMPUTER] Id=1 HostName=10.0.8.46

[COMPUTER] Id=2 HostName=ticker5-test

[NDBD DEFAULT] NoOfReplicas= 1 RedoBuffer=128M

[MYSQLD DEFAULT] [NDB_MGMD DEFAULT] [TCP DEFAULT]

[NDB_MGMD] ExecuteOnComputer=1 PortNumber=2200

[NDBD] ExecuteOnComputer=1 DataDir= /usr/local/mysql-cluster DataMemory=800M IndexMemory=640M

[NDBD] ExecuteOnComputer=2 DataDir= /usr/local/mysql-cluster DataMemory=800M IndexMemory=640M

[MYSQLD] ExecuteOnComputer=1

[MYSQLD] ExecuteOnComputer=2

If the reason for the failure is dues to attempting to load so much data in one transaction, what parameters can I adjust to allow it? It is not feasible for me to break up the data files into smaller chunks for loading, as I have 6 more tables to load with 3-6 million records each.

Also, my application reading the data will need to query as much as 10,000 records at a time? Are there parameters I need to adjust to allow querying this much data?

Thanks for any help you can provide.

Sandi