|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related
|
|
|
|
This issue is related to:
|
|
TREP-361
MySQLExtractor does not properly hand...
|
|
|
|
TREP-363
Log_event.read_log_event sometimes fa...
|
|
|
|
|
|
|
Sub-Tasks:
|
All
|
Open
|
|
| Sub-Task Progress: |
|
|
I occasionally get errors from the mysql extractor.
This is some extra logging that shows the problem :
INFO | jvm 1 | 2009/08/18 17:53:18 | 2009-08-18 17:53:18,391 WARN extractor.mysql.Log_event Trying to read more bytes (1037) than available in the file
(282)
INFO | jvm 1 | 2009/08/18 17:53:18 | com.continuent.tungsten.replicator.extractor.mysql.MySQLExtractException: EOFException while reading 1037 bytes fro
m binlog
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.extractor.mysql.Log_event.read_log_event(Log_event.java:335)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.extractor.mysql.MySQLExtractor.processFile(MySQLExtractor.java:350)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.extractor.mysql.MySQLExtractor.extractEvent(MySQLExtractor.java:470)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.extractor.mysql.MySQLExtractor.extract(MySQLExtractor.java:758)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.thl.THL.getLocalEvents(THL.java:339)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.thl.THL.run(THL.java:433)
INFO | jvm 1 | 2009/08/18 17:53:18 | at java.lang.Thread.run(Thread.java:595)
INFO | jvm 1 | 2009/08/18 17:53:18 | Caused by: java.io.EOFException
INFO | jvm 1 | 2009/08/18 17:53:18 | at java.io.DataInputStream.readFully(DataInputStream.java:178)
INFO | jvm 1 | 2009/08/18 17:53:18 | at java.io.DataInputStream.readFully(DataInputStream.java:152)
INFO | jvm 1 | 2009/08/18 17:53:18 | at com.continuent.tungsten.replicator.extractor.mysql.Log_event.read_log_event(Log_event.java:318)
INFO | jvm 1 | 2009/08/18 17:53:18 | ... 6 more
It seems that we try to read data from mysql binlog more quickly than it is really available.
As a consequence, I then got an OOM error as shown by this second log extract :
INFO | jvm 1 | 2009/08/18 17:53:18 | 2009-08-18 17:53:18,402 WARN extractor.mysql.Log_event Event length (with header) is : 1281903144
INFO | jvm 1 | 2009/08/18 17:53:18 | 2009-08-18 17:53:18,402 WARN extractor.mysql.Log_event Event length (without header) is : 1281903125
INFO | jvm 1 | 2009/08/18 17:53:18 | 2009-08-18 17:53:18,532 ERROR replicator.thl.THL THL thread failed
INFO | jvm 1 | 2009/08/18 17:53:18 | java.lang.OutOfMemoryError: Java heap space
It seems that following this first error, we try to extract again from the binlog, and then the size of the event to be read can not be handled
|
|
|
Bug
Major
MySQLExtractor may fail with an IOException while extracting an event from the binlog, showing a "binlog read error" message in the logs
Sub-task
