Comment 10 for bug 1281810
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote Re: Loss of records with LOAD INTO using trx split in 5.6 | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Also can reproduce the original issue with fewer rows - 10004
MySQL [test4]> set autocommit=0;
Query OK, 0 rows affected (0.00 sec)
MySQL [test4]> load data infile '/tmp/t2' into table tbtest1;
Query OK, 10004 rows affected (1.82 sec)
Records: 10004 Deleted: 0 Skipped: 0 Warnings: 0
MySQL [test4]> set autocommit=1;
(exit the client)
2014-02-19 17:06:16 19006 [Note] WSREP: forced trx split for LOAD: load data infile '/tmp/t2' into table tbtest1
[New Thread 0x7fff7effd700 (LWP 19096)]
[Thread 0x7fff7effd700 (LWP 19096) exited]
2014-02-19 17:06:22 19006 [Warning] MySQL is closing a connection that has an active InnoDB transaction. 4 row modifications will roll back.