Bug #30828 | Problem Replicating Data after a LOAD DATA statement, error reading log file | ||
---|---|---|---|
Submitted: | 5 Sep 2007 12:02 | Modified: | 4 Oct 2007 15:16 |
Reporter: | Dinko Ostric | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.0.41-community-nt | OS: | Windows (WINDOWS 2003 Server, SP 1) |
Assigned to: | CPU Architecture: | Any | |
Tags: | error 1236, error reading log, LOAD DATA, replication, windows 2003 |
[5 Sep 2007 12:02]
Dinko Ostric
[6 Sep 2007 6:03]
Valeriy Kravchuk
Thank you for a problem report. Please, check if this is a duplicate of bug #30435. Namely, compare values of read_buffer_size on different machines and sizes of files loaded.
[3 Oct 2007 7:05]
Dinko Ostric
The problem described in this bug was in: read_buffer_size, read_rnd_buffer_size, sort_buffer_size. It seems that if the values of buffer sizes are not set properly (larger - in MB or GB) the error happens. After setting the buffers to lover values (128 / 512 / 512 KB) replication started to work perfectly. It still replicates after several weeks. Problem solved. This bug is similar to Bug #8215, only that the error message is different and harder to solve. (only load data in file statement breaks the replication...)
[3 Oct 2007 18:14]
Valeriy Kravchuk
So, this looks more like a misconfiguration issue, not a bug.
[4 Oct 2007 15:16]
Dinko Ostric
Hi, I am not sure about your opinion because everything replicates fine till the LOAD DATA statement is performed. Also if the server (master server!) is misconfigured It should report in the error log something about that. The only thing that is reported as an error is on the SLAVE!! server: "Error reading packet from server: error reading log entry (server_errno=1236)...". It took us time to locate the problem, and also It took us time to find the solution. If the buffer parameters (on the MASTER) are huge and the master server can't handle that parameters it should warn about that, but instead only the slave server trows an error as stops replicating. The master server continues to write the log file, logging all queries (not throwing any errors), but the slaves can't read it from the moment of the LOAD DATA statement. I am not sure if the server builds the log (not warning about any error) and the slave can't read that log, the only! problem is in misconfiguration.