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

cmapi packages with single node installation causes DBRM readonly error

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 6.2.2, 6.3.1, cmapi-1.5, cmapi-1.6
    • cmapi-22.08.1
    • cmapi
    • None
    • 2021-17

    Description

      Build tested: MCS 6.2.2, 6.3.1
      cmapi: 1.5, 1.6
      OS: I have been testing with Ubuntu 18.04.

      For single node installation, cmapi package is installed, the node would end up in a DBRM readonly state. Starting the cmapi server or not does not make a difference.

      The simplest way to reproduce this is to just install all the deb packages, then run DDL statements. DBRM readonly error will occur.

      Although cmapi is not required for single-node installation, there is a high chance that user's would just install all packages download, causing this issue.

      I did not see the same issue with multiple-node installation, which requires cmapi.

      So far, I did the following columnstore and cmapi combinations:

      6.2.2-1 1.4 single-node passed
      6.2.2-1 1.4 multi-node passed

      6.2.2-1 1.5 singl-enode failed
      6.2.2-1 1.5 multi-node passed

      6.3.1-1 1.5 single-node failed
      6.3.1-1 1.5 multi-node passed

      6.3.1-1 1.6 single-node failed
      6.3.1-1 1.6 multi-node passed

      The issue was not identified previously because for single-node installation, cmapi was not installed since it was not required.

      Attachments

        Activity

          People

            alan.mologorsky Alan Mologorsky
            dleeyh Daniel Lee (Inactive)
            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.