You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a large MySQL binlog file (FILESIZE: 328035862 Bytes) which is being read and processed through a zongji application. Also, I am storing the binlog position to which events have been processed in an external memory. During this, a stage comes when my zongji application crashes as it goes out to heap memory because of a large number of unprocessed binlog events. When I restart the zongji application using the last processed binlogName and binlogNextPos, zongji starts reading the binlog events somewhere at the end of passed binlogName file skipping over the file.
Any ideas why this might be happening and how can I prevent this?
eg.
last processed event before zongji application crash : (mysql-bin-changelog.011531, 911301)
After restarting the application with the above binlogName and binlogNextPos, next event processed : (mysql-bin-changelog.011531,329171477)
The text was updated successfully, but these errors were encountered:
I have a large MySQL binlog file (FILESIZE: 328035862 Bytes) which is being read and processed through a zongji application. Also, I am storing the binlog position to which events have been processed in an external memory. During this, a stage comes when my zongji application crashes as it goes out to heap memory because of a large number of unprocessed binlog events. When I restart the zongji application using the last processed binlogName and binlogNextPos, zongji starts reading the binlog events somewhere at the end of passed binlogName file skipping over the file.
Any ideas why this might be happening and how can I prevent this?
eg.
last processed event before zongji application crash : (mysql-bin-changelog.011531, 911301)
After restarting the application with the above binlogName and binlogNextPos, next event processed : (mysql-bin-changelog.011531,329171477)
The text was updated successfully, but these errors were encountered: