• Dmitry Lenev's avatar
    Fix for bug #51134 "Crash in MDL_lock::destroy on a concurrent · 22bc48b2
    Dmitry Lenev authored
    DDL workload".
    
    When a RENAME TABLE or LOCK TABLE ... WRITE statement which
    mentioned the same table several times were aborted during 
    the process of acquring metadata locks (due to deadlock 
    which was discovered or because of KILL statement) server 
    might have crashed.
    
    When attempt to acquire all locks requested had failed we
    went through the list of requests and released locks which
    we have managed to acquire by that moment one by one. Since 
    in the scenario described above list of requests contained 
    duplicates this led to releasing the same ticket twice and 
    a crash as result.
    
    This patch solves the problem by employing different approach
    to releasing locks in case of failure to acquire all locks
    requested. 
    Now we take a MDL savepoint before starting acquiring locks 
    and simply rollback to it if things go bad.
    22bc48b2
lock_multi.test 26.5 KB