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

TRANSACTION sometimes stay in "KILLLED' STATE for inifinitve time!

    XMLWordPrintable

Details

    Description

      Hi dudes, after upgrade from mariadb 10.1 to 10.2.8, some simple transaction is running for infinitive times...

      SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST where Time > 9000\G

      I have 19 transaction that is running for this time

      they won't die with kill command..

                 ID: 10245887
      		 
               USER: novid
      		 
               HOST: 
                 DB: api
      		 
            COMMAND: Killed
      		 
               TIME: 106767
      		 
              STATE: NULL
      		 
               INFO: insert into `driver_status_changelog` (`status`, `driver_id`, `updated_at`, `created_at`) values ('4', '65767', '2017-09-06 09:22:04', '2017-09-06 09:22:04')
      		 
            TIME_MS: 106767343.552
      		 
              STAGE: 0
      		 
          MAX_STAGE: 0
      		 
           PROGRESS: 0.000
      		 
        MEMORY_USED: 92848
      		 
      EXAMINED_ROWS: 0
      		 
           QUERY_ID: 300183941
      		 
        INFO_BINARY: insert into `driver_status_changelog` (`status`, `driver_id`, `updated_at`, `created_at`) values ('4', '65767', '2017-09-06 09:22:04', '2017-09-06 09:22:04')
      		 
                TID: 15109

      and with SHOW ENGINE INNODB STATUS\G

      ---TRANSACTION 46385651188, ACTIVE 107004 sec
      		 
      8 lock struct(s), heap size 1136, 4 row lock(s), undo log entries 4
      		 
      MySQL thread id 10245887, OS thread handle 0x7f898dcb6700, query id 300183941 api
      		 
      insert into `driver_status_changelog` (`status`, `driver_id`, `updated_at`, `created_at`) values ('4', '65767', '2017-09-06 09:22:04', '2017-09-06 09:22:04')
      		 
      Trx read view will not see trx with id >= 46385651191, sees < 46385650307

      changing in these transaction is so small (2 or 3) so waiting is not for transaction rollback.

      Thread stay in killed state and so some record is lock for infinitive time

      Attachments

        1. my.cnf
          6 kB
        2. innodb-status
          48 kB
        3. before-restart.gdb
          90 kB
        4. before.gdb
          92 kB
        5. after-restart.gdb
          67 kB
        6. after.gdb
          92 kB
        7. 43205.gdb
          114 kB
        8. 42003.gdb
          97 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11896 thd_get_error_context_description race condition

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13983 Mariadb becomes unresponsive

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              novid novid
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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