MySQL Forums
Forum List  »  Replication

Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND
Posted by: amritansu ray
Date: April 10, 2012 04:04AM

Hi,

We are receiving the following error in our replication. We have MASTER-MASTER replication.

Could not execute Update_rows event on table bfly.iar_async_email_sequence; Can't find reco
rd in 'iar_async_email_sequence', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log binlog.005988,
end_log_pos 13081, Error_code: 1032

The exact error is

Slave_IO_State: Waiting for master to send event
Master_Host: ip_address (hidden)
Master_User: repl
Master_Port: 3309
Connect_Retry: 60
Master_Log_File: binlog.006056
Read_Master_Log_Pos: 106
Relay_Log_File: relay-bin.184580
Relay_Log_Pos: 13047
Relay_Master_Log_File: binlog.005988
Slave_IO_Running: Yes
Slave_SQL_Running: No
Replicate_Do_DB:
Replicate_Ignore_DB: viptest
Replicate_Do_Table:
Replicate_Ignore_Table: ssdb_admin.tomcat_sessions
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 1032
Last_Error: Could not execute Update_rows event on table bfly.iar_async_email_sequence; Can't find record in 'iar_async_email_sequence', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log binlog.005988, end_log_pos 13081
Skip_Counter: 0
Exec_Master_Log_Pos: 12905
Relay_Log_Space: 740417
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 1032
Last_SQL_Error: Could not execute Update_rows event on table bfly.iar_async_email_sequence; Can't find record in 'iar_async_email_sequence', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log binlog.005988, end_log_pos 13081


Our error log has the following information

120409 10:46:13 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=130023424
read_buffer_size=1048576
max_used_connections=154
max_threads=1500
threads_connected=120
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 26254022 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

120409 10:46:20 mysqld_safe mysqld restarted
120409 10:46:20 [Warning] The syntax '--log' is deprecated and will be removed in MySQL 7.0. Please use '--general_log'/'--gen
eral_log_file' instead.
120409 10:46:20 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_q
uery_log'/'--slow_query_log_file' instead.
InnoDB: Log scan progressed past the checkpoint lsn 360 2876185512
120409 10:46:24 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 360 2876190490
120409 10:46:24 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 20920, file name /u999/mysdata/3309/binlog.031270
120409 10:46:31 InnoDB: Started; log sequence number 360 2876190490
120409 10:46:31 [Note] Recovering after a crash using /u999/mysdata/3309/binlog
120409 10:46:31 [Note] Starting crash recovery...
120409 10:46:31 [Note] Crash recovery finished.
120409 10:46:31 [Note] Slave SQL thread initialized, starting replication in log 'binlog.005988' at position 106, relay log '/
u999/mysdata/3309/relay-bin.184578' position: 208

After this there is replication error. The DB crashed some how and after recovery its having the Error 1032.

The same error is present in the second master also.

The version of both the dbs are 5.1.32-enterprise-gpl-advanced-log and its pre existing. Never been upgraded from an older version.

Please suggest.



Edited 1 time(s). Last edit at 04/10/2012 04:09AM by amritansu ray.

Options: ReplyQuote


Subject
Views
Written By
Posted
Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND
70795
April 10, 2012 04:04AM


Sorry, you can't reply to this topic. It has been closed.

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.