Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-23930

i have a rollback running for over 30 hours

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      the client was running a create table and decided to kill it off. this was yesterday morning. the rollback is still running accumulating time. the backup last night got hung on it so that was canceled. this is from the show processlist…

      +--------+-------------+------------------------------+------+------------+--------+--------------------+-------------------------------------------------------------------------------------+----------+ 
       | Id | User | Host | db | Command | Time | State | Info | Progress | 
       +--------+-------------+------------------------------+------+------------+--------+---------------------+------------------------------------------------------------------------------------+----------+ 
       | 302993 | js345e | % | prc | Killed | 91827 | Rollback | create table x_qm_trx_stg (primary key (std_addr_id,sfdc_sp_acct_id,product | 0.000 | 
      

      in addition this is from the instance log...

      2020-10-07 10:58:07 302993 [Note] InnoDB: Deferring DROP TABLE `prc`.`x_qm_trx_stg`; renaming to prc/#sql-ib12219315

      He says it had been running between 1-2 hours before he killed it.

      I've attached the process which keeps accumulating time to it.

      we won't try taking another backup till it completes or you tell me how to stop it.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mn1357 Michael Necklas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.