Bug #11690 Weird error dropping database: REPL$BANK/ACCOUNT_TYPES Error Code: 4710
Submitted: 1 Jul 2005 14:13 Modified: 12 Jul 2005 13:41
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.0-wl2325-wl1354-new OS:Linux (Linux)
Assigned to: Tomas Ulin CPU Architecture:Any

[1 Jul 2005 14:13] Jonathan Miller
Description:
No issue in this case...   but please bug-report, there should be 
nothing like this in the errorlog (but I know why it happens)...

Tomas

Jonathan Miller wrote:

>Okay, A little more information for you. I get these when:
>
>1) I create the database on the slave: CREATE DATABASE BANK;
>2) Restore cluster BACK UP to the slave from Master.
>3) Drop the BANK database on the slave;
>
>Not sure that there is a real problem here, but just did not like 
>seeing these in the error log.
>
>Thanks
>JBM
>
>  
>
>>-----Original Message-----
>>From: Tomas Ulin [mailto:tomas@mysql.com]
>>Sent: Friday, July 01, 2005 9:21 AM
>>To: Jonathan Miller
>>Cc: 'Jonas Oreland'; 'Martin Skold'
>>Subject: Re: FW: Weird error dropping database
>>
>>J,
>>
>>this will happen if there are no events created for the replication...
>>the "drop table" expects to be able to drop also the events and prints 
>>this error.
>>
>>Can happen  for the follwoing reasons:
>>- the mysqld who created the tables did not create the events (if so a 
>>bug there)
>>- I can imagine cases when tables have been created with ndb_restore...
>>so that the events have not been created... have to look at this
>>
>>
>>T
>>
>>Jonathan Miller wrote:
>>
>>    
>>
>>>Any ideas?
>>>
>>>
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: Mats Kindahl [mailto:mats@mysql.com]
>>>>Sent: Friday, July 01, 2005 2:16 AM
>>>>To: Jonathan Miller
>>>>Subject: Re: Weird error dropping database
>>>>
>>>>Jonathan Miller wrote:
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>>>Mats,
>>>>>
>>>>>On the slave I issue:
>>>>>
>>>>>Stop slave;
>>>>>Drop database BANK;
>>>>>
>>>>>In the mysqld error log I get:
>>>>>050630 21:43:29 [ERROR] NDB Binlog: Unable to drop event in database.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Event:
>>>>
>>>>
>>>>        
>>>>
>>>>>REPL$BANK/ACCOUNT Error Code: 4710 Message: Event not found 050630 
>>>>>21:43:29 [ERROR] NDB Binlog: Unable to drop event in database.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Event:
>>>>
>>>>
>>>>        
>>>>
>>>>>REPL$BANK/ACCOUNT_TYPES Error Code: 4710 Message: Event not found 
>>>>>050630 21:43:29 [ERROR] NDB Binlog: Unable to drop event in database.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Event:
>>>>
>>>>
>>>>        
>>>>
>>>>>REPL$BANK/GL Error Code: 4710 Message: Event not found 050630 
>>>>>21:43:29 [ERROR] NDB Binlog: Unable to drop event in database.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Event:
>>>>
>>>>
>>>>        
>>>>
>>>>>REPL$BANK/SYSTEM_VALUES Error Code: 4710 Message: Event not found 
>>>>>050630 21:43:30 [ERROR] NDB Binlog: Unable to drop event in database.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Event:
>>>>
>>>>
>>>>        
>>>>
>>>>>REPL$BANK/ACCOUNT_TYPE Error Code: 4710 Message: Event not found
>>>>>
>>>>>Not sure there is an issue here, but I did not expect to see these
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>errors.
>>>>
>>>>
>>>>        
>>>>
>>>>>Thoughts?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Just "it looks like a cluster problem". :)
>>>>
>>>>I just don't recognize the error message and, specifically, since it 
>>>>starts with "NDB Binlog", I think this is some clusterism that I'm 
>>>>not familiar with.
>>>>
>>>>/Matz
>>>>
>>>>
>>>>        
>>>>
>>>
>>>      
>>>

How to repeat:
>1) I create the database on the slave: CREATE DATABASE BANK;
>2) Restore cluster BACK UP to the slave from Master.
>3) Drop the BANK database on the slave;

Suggested fix:
Don't show error if it is not an issue :-)
[11 Jul 2005 11:15] Tomas Ulin
proposed solution is to let ndb_restore create the events during restore of metadata