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

SET_DBROOT_STATUS: DBroot not valid error being reported

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Fix
    • 1.2.2
    • Icebox
    • ?
    • None
    • 1um 4pm external memory

    Description

      Customer reporting error log

      Jan 10 12:20:54 nvm002315 ProcessMonitor[27772]: 54.832372 |0|0|0| E 18 CAL0000:
      statusControl: SET_DBROOT_STATUS: DBroot not valid: 3
      Jan 10 12:20:59 nvm002315 ProcessMonitor[27772]: 59.785275 |0|0|0| E 18 CAL0000:
      statusControl: SET_DBROOT_STATUS: DBroot not valid: 4

      mcsadmin> getStorageconfig
      getstorageconfig Tue Jan 22 07:43:42 2019

      System Storage Configuration

      Performance Module (DBRoot) Storage Type = external
      System Assigned DBRoot Count = 4
      DBRoot IDs assigned to 'pm1' = 1
      DBRoot IDs assigned to 'pm2' = 2
      DBRoot IDs assigned to 'pm3' = 3
      DBRoot IDs assigned to 'pm4' = 4

      getStorageconfig not so good

      Component Status Last Status Change
      ------------ -------------------------- ------------------------
      DBRoot #1 ACTIVE Wed Jan 30 12:20:36 2019
      DBRoot #2 ACTIVE Wed Jan 30 12:20:46 2019

      Couldnt reproduce issue

      1. tried starting with 2 dbroots and adding 2, didnt see the problem.
      2. took customer Columnstore.xml and placed oan exact system inhouse, didnt see the problem.

      customer reports they have rebooted and problem doesnt go ahead.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hill David Hill (Inactive)
            Votes:
            1 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.