MySQL Forums
Forum List  »  NDB clusters

cluster fails after 1st query
Posted by: Balasubramanian Azhagappan
Date: March 01, 2005 10:49AM

Hello,
I configured a cluster in 2 Sunfire E2900, 16G Ram, 4 Dual core processors running Solaris 9, 64bit. Each SunFire machine was allocated 2 ndb nodes and 1 mysqld.

MYSQL version i installed is mysql-max-4.1.10 64 bit version for solaris.

Initially, I gave the value for [NDB DEFAULT] as

------------------------------------------
DataMemory : 3500M
IndexMemory: 700M
------------------------------------------

and i have 6 tables in the cluster database. I populated with 3 Million Entries in each table.

Every thing was working fine. As i had 16G ram, i thought of increasing the memory for the ndb nodes and want to insert more records in the cluster database.

Then i made the following changes

------------------------------------------
DataMemory : 5G
IndexMemory: 1G
------------------------------------------

Then, restarted the cluster. The cluster started successfully.
But as soon as i made my first query from the console of mysql

------------------------------------------
mysql>select count(*) from CFG; (Where CFG is one of the 6 tables i have)
------------------------------------------

all the cluster nodes crashed and in the logs i could find the following message

------------------------------------------
Type Of Error: error
Message : pointer too large
------------------------------------------

Then, fearing that the problem was due to increasing the datamemory size, i reverted the values of DataMemory and IndexMemory to their previous values itself

Then also, after the cluster starting successfully, on the same query, i get the same error.

what could be possibly wrong here ?

regards,
bala

Options: ReplyQuote


Subject
Views
Written By
Posted
cluster fails after 1st query
2701
March 01, 2005 10:49AM


Sorry, you can't reply to this topic. It has been closed.

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.