MySQL Bugs: #19146: No error issued where BackupWriteSize has inappropriate value

Bug #19146	No error issued where BackupWriteSize has inappropriate value
Submitted:	17 Apr 2006 18:47	Modified:	8 Feb 2007 2:19
Reporter:	Serge Kozlov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.9 (beta)	OS:	Linux (Linux FC4)
Assigned to:	Guangbao Ni	CPU Architecture:	Any

Description:
If BackupWriteSize variable has too small value (less 512) or very large (1G) then data nodes can't start and error.log contains:

Current byte-offset of file-pointer is: 568

Time: Monday 17 April 2006 - 20:31:24
Status: Temporary error, restart node
Message: Internal program error (failed ndbrequire) (Internal error, programming
 error or missing error message, please report a bug)
Error: 2341
Error data: backup/Backup.cpp
Error object: BACKUP (Line: 2199) 0x0000000e
Program: /home/ndbdev/skozlov/builds/libexec/ndbd
Pid: 11704
Trace: /space/run/ndb_3_trace.log.1
Version: Version 5.1.9 (beta)
***EOM***

How to repeat:
Try to start a cluster for following configuration:

[ndbd default]
NoOfReplicas: 1
IndexMemory: 50M
DataMemory: 100M
DataDir: /space/run
FileSystemPath: /space/run
BackupWriteSize: 1

[mgm default]
ArbitrationRank: 1
DataDir: /space/run

[ndb_mgmd]
Id: 1
HostName: ndb16

[ndbd]
Id: 2
HostName: ndb16

[ndbd]
Id: 3
HostName: ndb16

[mysqld]
Id: 15
HostName: ndb16

Suggested fix:
Probably have to add limitations for BackupWriteSize as for others.

Cluster handles wrong configurations by shutting down nodes

Part of setting up cluster for an application is to test out which
applicaiton that works.

This is not something that will change anytime soon.

However you should get an appropriate error message when the node goes
down.

I'm therefore relableing the bug and setting different prio

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/13710

ChangeSet@1.2290, 2006-10-13 17:40:57+08:00, gni@dev3-127.(none) +1 -0
  BUG #19146 If Backup parameters incorrectly set, the data nodes can't start.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/13711

ChangeSet@1.2290, 2006-10-16 09:31:50+08:00, gni@dev3-127.(none) +1 -0
  BUG #19146 If Backup parameters incorrectly set, the data nodes can't start.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/14796

ChangeSet@1.2290, 2006-11-03 19:08:57+08:00, gni@dev3-127.(none) +2 -0
  BUG #19146 If Backup parameters incorrectly set, the data nodes can't start.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/16933

ChangeSet@1.2340, 2006-12-14 18:10:18+08:00, gni@dev3-221.dev.cn.tlan +2 -0
  BUG #19146 If Backup parameters incorrectly set, the data nodes can't start.

pushed to 5.1.16

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Based on Tomas' remarks:

Documented in 5.1.16 changelog as "In the event that cluster backup parameters such as BackupWriteSize were incorrectly set, no appropriate error was issued to indicate that this was the case."

Updated bug synopsis.