Bug #25357 ndbd node cannot restart with disk tables
Submitted: 2 Jan 2007 4:20 Modified: 14 Jun 2007 18:44
Reporter: Jason Downing Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S3 (Non-critical)
Version:5.1.14 OS:Linux (Debian 2.6.18.1)
Assigned to: CPU Architecture:Any
Tags: ndbd node cannot restart with disk tables

[2 Jan 2007 4:20] Jason Downing 
Description:
This bug appears to be the same as 21271, except that 21271 was for version 5.1.11, and is supposed to be fixed. I don't know if the cause is the same but the symptoms are.

An ndbd node cannot be restarted after taking it offline. Config.ini:

[NDBD DEFAULT]
NoOfReplicas=1
DataMemory=500M
IndexMemory=100M
MaxNoOfAttributes=3000
MaxNoOfConcurrentOperations=1000000
MaxNoOfConcurrentTransactions=100000
LockPagesInMainMemory: Yes
StartFailureTimeout=1000000
StartPartialTimeout=200000
LogLevelStartup=15
LogLevelShutdown=15
LogLevelStatistic=15
LogLevelCheckpoint=15
LogLevelNodeRestart=15
LogLevelConnection=15
LogLevelError=15
LogLevelInfo=15
StopOnError=N

[NDB_MGMD]
hostname=192.168.0.12
datadir=/var/lib/mysql-cluster
Id=17

[NDBD]
hostname=192.168.0.13
datadir=/usr/local/mysql/data
Id=10

[MYSQLD]
hostname=192.168.0.12
Id=12

Cluster or node will restart with --initial

How to repeat:
Use my test setup, online now. See log in details below
[16 Jan 2007 3:37] Jason Downing 
Sorry, I need the machines I had set up. You'll have to find another way to replicate this bug. Regards, Jason
[23 Jan 2007 18:05] Bugs System 
This looks to be the same as bug #25710 "Restarting data node _always_ requires --initial".

Are others seeing this problem? This is making changing cluster parameters very time consuming.
[14 May 2007 18:44] Tomas Ulin 
Jason,

can you please try to reproduce this using the latest version, and provide us with the way to reproduce.

BR,

Tomas
[14 Jun 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".