Skip to content
  • Debarun Banerjee's avatar
    2e785b3e
    BUG#25032066 PREPARED TRANSACTION SHOULD NOT BE ROLLED BACK · 2e785b3e
    Debarun Banerjee authored
    
                 BY HIGH PRIORITY TRANSACTION
    
    Problem :
    ---------
    1. delete_all_rows() and rnd_init() are not returning error
    after async rollback in 5.7. This results in assert in
    innodb in next call.
    
    2. High priority transaction is rolling back prepared transaction.
    This is because TRX_FORCE_ROLLBACK_DISABLE is getting set only for
    first entry [TrxInInnoDB].
    
    Solution :
    ----------
    1. return DB_FORCED_ABORT error after rollback.
    2. check and disable rollback in TrxInInnodb::enter always.
    
    Reviewed-by: default avatarSunny Bains <sunny.bains@oracle.com>
    
    RB: 13777
    (cherry picked from commit 628f957a874dfcdc5431c52a39b5363c13a1fdba)
    2e785b3e
    BUG#25032066 PREPARED TRANSACTION SHOULD NOT BE ROLLED BACK
    Debarun Banerjee authored
    
                 BY HIGH PRIORITY TRANSACTION
    
    Problem :
    ---------
    1. delete_all_rows() and rnd_init() are not returning error
    after async rollback in 5.7. This results in assert in
    innodb in next call.
    
    2. High priority transaction is rolling back prepared transaction.
    This is because TRX_FORCE_ROLLBACK_DISABLE is getting set only for
    first entry [TrxInInnoDB].
    
    Solution :
    ----------
    1. return DB_FORCED_ABORT error after rollback.
    2. check and disable rollback in TrxInInnodb::enter always.
    
    Reviewed-by: default avatarSunny Bains <sunny.bains@oracle.com>
    
    RB: 13777
    (cherry picked from commit 628f957a874dfcdc5431c52a39b5363c13a1fdba)
Loading