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

system status does not consider innodb recovery

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.5
    • Fix Version/s: N/A
    • Component/s: oam
    • Labels:

      Description

      In 1.0.5 after a failed transaction and crash recovery, restartSystem doesn't wait for mysql to restart properly.

      System and Module statuses

      Component Status Last Status Change
      ------------ -------------------------- ------------------------
      System ACTIVE Thu Dec 1 01:13:30 2016

      Module um1 ACTIVE Thu Dec 1 01:13:26 2016
      Module pm1 ACTIVE Thu Dec 1 01:13:08 2016
      Module pm2 ACTIVE Thu Dec 1 01:13:15 2016

      Active Parent OAM Performance Module is 'pm1'

      2016-12-01 1:12:16 140036511479552 [Note] InnoDB: FTS optimize thread exiting.
      2016-12-01 1:12:16 140036570851072 [Note] InnoDB: Starting shutdown...
      6 7 82016-12-01 1:13:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish
      92016-12-01 1:14:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish
      2016-12-01 1:15:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dthompson David Thompson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.