MySQL Bugs: #16352: DD: --initial does not clear out Disk Data files/logs

Bug #16352	DD: --initial does not clear out Disk Data files/logs
Submitted:	10 Jan 2006 20:02	Modified:	1 Feb 2006 16:16
Reporter:	Jonathan Miller	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.5-alpha	OS:	Linux (Linux)
Assigned to:	Jonathan Miller	CPU Architecture:	Any

Description:
According to the 5.1 Docs --initial:
this parameter will cause the node to delete ***"any"*** file created by earlier ndbd  instances needed for recovery, including the recovery log files.

I see no reason not to the data file as the cluster will no longer have knowleadge of it and will not be able to use it. 

In addition,  The use will not be able to create files with the same name and will get a failure.

How to repeat:
Create a LG and TS with datafile. Restart the cluster using --initial. Try to create the same LG and TS, or try to access it.

Suggested fix:
--initial does as the docs says and delete ***"any"*** file created by earlier ndbd  instances

The documentation is wrong. It does not remove all files created by earlier ndb processes.
It removes _all_ files in the ndb_X_fs directory... (i implemented it)

I think that's a bad practice, that we should move away from.

The undofiles and data files are created in those directories. What good are these files once --initial had been done?

open https://intranet.mysql.com/worklog/NDB-BackLog/index.pl?tid=3131 in place of this

Work Log 3131 has been open to correct this in future release

Customers are also have issues with this:

http://bugs.mysql.com/bug.php?id=18851