Lost Data with delayed insert or mysqlhotcopy or lock and flush ?
MSSQL’s mysqlhotcopy utility causes the handler who manages the ‘delayed insert statements’ to terminate with a message -“Delayed insert thread couldn\'t get requested lock for”.
I have worked with MSSQL’s mysqlhotcopy (to backup database) utility many times but it does not failed. But this time it seems that while acquiring lock (waiting for a query to finish its job) another delayed insert statement (may involve two or more tables) may be triggered which might cause the server to throw an error message as mentioned above with loss of data.
Another assumption could be that in order to clear the buffer for the backup also termed as ‘Flushing’ and to reload the cache for the backup process the delayed insert statement might have flushed which cause the server to throw an error message with loss of data.


