5.1 test servers "starting" for 3 hours

From: Brian Moon <brianm(at)dealnews.com>
Date: Mon Jul 02 2007 - 20:00:15 EDT

Hi all,

I have just set up a 5.1 cluster to start testing against. We are drooling over disk based data. We have several tables with blobs that are not often used, but are taking up a lot of space. Plus all the other cool features that I have not even touched upon yet.

Anyhow, I started the ndbd --initial over 3 hours ago. The manager still says starting for both nodes. Its just a two node cluster. Here is the config.ini. Mostly copied from our production cluster. This is my first foray with 5.1. If I have messed it up I don't want to waste a night on it.

[NDBD DEFAULT]

NoOfReplicas=2
DataMemory=2560MB
IndexMemory=512MB
MaxNoOfTables=1024
MaxNoOfAttributes=10000
TimeBetweenLocalCheckpoints=6
MaxNoOfConcurrentOperations=100000
MaxNoOfLocalOperations=200000
[MYSQLD DEFAULT]
[NDB_MGMD DEFAULT]
[TCP DEFAULT]

# Managment Server
[NDB_MGMD]

HostName=staging2 # the IP of THIS SERVER # Storage Engines
[NDBD]

HostName=mtest1                # the IP of the FIRST SERVER

DataDir=/dealnews/mysql-cluster
[NDBD]

HostName=mtest2                # the IP of the SECOND SERVER

DataDir=/dealnews/mysql-cluster
# 2 MySQL Clients
# I personally leave this blank to allow rapid changes of the mysql clients;
[MYSQLD]
[MYSQLD]

-- 

Brian Moon
Senior Developer
------------------------------
http://dealnews.com/
It's good to be cheap =)

-- 
MySQL Cluster Mailing List
For list archives: 
http://lists.mysql.com/cluster
To unsubscribe:    
http://lists.mysql.com/cluster?unsub=lists@pantek.com

Received on Mon Jul 2 20:00:30 2007