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

Reduced systemd timeouts results in corrupted EM

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.6.5, 6.3.1
    • Fix Version/s: 5.6.6, 6.4.1
    • Component/s: DMLProc
    • Labels:
      None
    • Sprint:
      2021-17

      Description

      There were multiple cases when low default startup/shutdown systemd timeouts, namely mcs-dmlproc, mcs-workernode, result in a lost or corrupted extent map.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MCOL-4775 DMLproc is unable to complete a rollback and goes into a crash loop

          • 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

          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-5093 mariadb services on column cluster nodes occasionally enters a restart loop

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              drrtuy Roman
              Reporter:
              drrtuy Roman
              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.