Bug #328 Replication stops if on the master we got "table is full" doing LOAD DATA inodb

Submitted: 26 Apr 2003 6:31 Modified: 26 Apr 2003 6:31
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: CPU Architecture:Any

[26 Apr 2003 6:31] Guilhem Bichot
Description:
When doing LOAD DATA INFILE into an InnoDB table, if it fails with "table is full", then replication stops.

When LOAD DATA INFILE failed in the master (AUTOCOMMIT=1):

mysql> load data infile '/home/heikki/rtdump' into table replt3;
ERROR 1114: The table 'replt3' is full
mysql>

the slave failed like this:

heikki@hundin:~/mysql-4.0/sql> mysqld --defaults-file=~/slavemy.cnf
021204 21:45:35  InnoDB: Started
mysqld: ready for connections
021204 21:45:35  Slave I/O thread: connected to master
'slaveuser@hundin:3307',
 replication started in log 'FIRST' at position 4
021204 22:04:22  Slave: Could not open file '/tmp/SQL_LOAD-2-1-4.data',
error_co
de=2
021204 22:04:22  Error running query, slave SQL thread aborted. Fix the
problem,
 and restart the slave SQL thread with "SLAVE START". We stopped at log
'binlog.
026' position 27

How to repeat:
[26 Apr 2003 6:31] Guilhem Bichot
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

fixed in 4.0.10

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.037 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.