Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-4775

DMLproc is unable to complete a rollback and goes into a crash loop

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 5.5.2
    • 6.4.1
    • DMLProc
    • None
    • 2021-9, 2021-10, 2021-11, 2021-12, 2021-13, 2021-14, 2021-15, 2021-16, 2021-17

    Description

      A customer experienced an issue where on cluster restart, DMLproc was unable to complete the rollback of 3 tables.
      It would try for a while and then die, then a new DMLproc would be spawned, over and over in a wash-rinse-repeat fashion:

      Jun 23 11:08:27 cluster-csx2 DMLProc[1123]: 27.889048 |0|0|0| I 20 CAL0002: DMLProc will rollback 0 tables.
      		 
      Jun 23 11:08:28 cluster-csx2 DMLProc[1123]: 28.280692 |0|0|0| I 20 CAL0002: DMLProc will rollback 3 transactions.
      		 
      Jun 23 11:08:43 cluster-csx2 DMLProc[1123]: 43.466989 |0|0|0| I 20 CAL0002: DMLProc will roll back transaction 24608
      		 
      Jun 23 11:09:58 cluster-csx2 DMLProc[1247]: 58.340083 |0|0|0| I 20 CAL0002: DMLProc starts rollbackAll.
      		 
      Jun 23 11:09:58 cluster-csx2 DMLProc[1247]: 58.386158 |0|0|0| I 20 CAL0002: DMLProc will rollback 0 tables.
      		 
      Jun 23 11:09:58 cluster-csx2 DMLProc[1247]: 58.770217 |0|0|0| I 20 CAL0002: DMLProc will rollback 3 transactions.
      		 
      Jun 23 11:10:02 cluster-csx2 DMLProc[1247]: 02.689347 |0|0|0| I 20 CAL0002: DMLProc will roll back transaction 24608
      		 
      Jun 23 11:11:28 cluster-csx2 DMLProc[1452]: 28.837884 |0|0|0| I 20 CAL0002: DMLProc starts rollbackAll.
      		 
      Jun 23 11:11:28 cluster-csx2 DMLProc[1452]: 28.891178 |0|0|0| I 20 CAL0002: DMLProc will rollback 0 tables.
      		 
      Jun 23 11:11:29 cluster-csx2 DMLProc[1452]: 29.273671 |0|0|0| I 20 CAL0002: DMLProc will rollback 3 transactions.

      You can see in the log that the process ID of DMLProc changes, but there are no traces in the log about it dying, no trace files, nothing.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MCOL-5105 Reduced systemd timeouts results in corrupted EM

          • Major - Major loss of function.
          • Closed
          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MCOL-5021 Implement an auxiliary (hidden) column to improve DELETE performance.

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MCOL-4867 DMLProc failed to rollback a txn

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MCOL-4785 ROLLBACK of a long lasting DML left cluster in unusable state

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              dleeyh Daniel Lee (Inactive)
              rpizzi Rick Pizzi (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              13 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.