MySQL Bugs: #60072: Use of Invalid values for limit memory option during apply-log step also passes

Bug #60072	Use of Invalid values for limit memory option during apply-log step also passes
Submitted:	10 Feb 2011 2:33	Modified:	16 Feb 2011 9:35
Reporter:	Hema Sridharan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	MEB 3.6	OS:	Any (Linux, Mac OS X)
Assigned to:	Thava Alagu	CPU Architecture:	Any

Description:
Execute mysqlbackup to directory
Now stop the server and apply logs for recovery
Use limit-memory option to specify the memory that can be used when applying logs
When invalid values of limit memory is used, still the test passes without any errors.

How to repeat:
1) ./mysqlbackup  --datadir=/export/home2/tmp/mysql-5.1-meb-testing/mysql-test/var/mysqld.1/backup/data/  --innodb_log_file_size=5M --innodb_log_files_in_group=4 --backup_innodb_log_files_in_group=4 --backup_innodb_log_file_size=5M --innodb_data_home_dir=/export/home2/tmp/mysql-5.1-meb-testing/mysql-test/var/mysqld.1/backup/data/ --backup-dir=/export/home2/tmp/meb-backups/bkpdir  --socket=/export/home2/tmp/mysql-5.1-meb-testing/mysql-test/var/tmp/mysqld.1.sock --user=root --port=13000 --protocol=tcp backup

2) Now stop the server and apply logs with limit-memory option
./mysqlbackup --backup-dir=/export/home2/tmp/meb-backups/bkpdir --limit-memory=abcdefghijklmnopqrstuvwxyz apply-log

Now also try different values for --limit-memory option like "abcdefghijklmnopqrstuvwxyz", 10293984584983754938482749327493758374837873834784875893754837648364787,
-3883439932929929,
23444.883883 etc.

Verified on Mac OS X:

macbook-pro:meb-3.6 openxs$ bin/mysqlbackup -uroot --backup-dir=/tmp/backup --limit-memory=abcdefghijklmnopqrstuvwxyz apply-log

InnoDB Backup Utility v3.6.0 [2011/02/10] 
Copyright (c) 2003, 2011, Oracle and/or its affiliates. All Rights Reserved.

INFO: Starting with following command line ...
 bin/mysqlbackup -uroot --backup-dir=/tmp/backup 
        --limit-memory=abcdefghijklmnopqrstuvwxyz apply-log 

IMPORTANT: Please check that mysqlbackup run completes successfully.
            At the end of a successful 'apply-log' run mysqlbackup
            prints "mysqlbackup completed OK!".

 mysqlbackup: INFO: Backup repository configuration: 
  datadir                          =  /tmp/backup
  innodb_data_home_dir             =  /tmp/backup
  innodb_data_file_path            =  ibdata1:10M:autoextend
  innodb_log_group_home_dir        =  /tmp/backup
  innodb_log_files_in_group        =  2
  innodb_log_file_size             =  5242880

110210 21:16:24 mysqlbackup: INFO:  ibbackup_logfile's creation parameters:
          start lsn 1745920, end lsn 1748731,
          start checkpoint 1746229.
InnoDB: Doing recovery: scanned up to log sequence number 1748731
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 Setting log file size to 0 5242880
Setting log file size to 0 5242880
 mysqlbackup: INFO: We were able to parse ibbackup_logfile up to
          lsn 1748731.
 mysqlbackup: INFO: The first data file is '/tmp/backup/ibdata1'
          and the new created log files are at '/tmp/backup/'
 mysqlbackup: INFO: System tablespace file format is Antelope.
110210 21:16:24 mysqlbackup: INFO: Full backup prepared for recovery successfully!

The problem has been fixed in the latest patch in the internal repository.