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

Assign DBRoot command failed - setFilesPerColumnPartition Failed

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 1.2.2
    • Fix Version/s: N/A
    • Component/s: oam
    • Labels:
      None
    • Environment:
      2um 3pm 1 dbroot per pm external SAN

      Description

      Customer has a system with 3 pms using 1 dbroot per with external storage. They wanted to add 3 more dbroots making 2 dbroot per pm.

      They got this error:

      root@usiadmdmaxp01:~# mcsadmin assignDbrootPmConfig 4 pm1
      assigndbrootpmconfig Thu Jan 17 15:41:44 2019

      DBRoot IDs assigned to 'pm1' = 1

      Changes being applied

      DBRoot IDs assigned to 'pm1' = 1, 4

      ERROR: old FilesPerColumnPartition not a multiple of DBRootCount

            • setFilesPerColumnPartition Failed
            • Failed Assign of DBRoots: API Failure return in assignPmDbrootConfig API

      I believe the error is coming from this check in the oam api setFilesPerColumnPartition

      if ( oldFilesPerColumnPartition != oldSystemDBRootCount *
      (oldFilesPerColumnPartition / oldSystemDBRootCount) )

      I think you arent allowed to change this setting of FilesPerColumnPartition to something that isnt a equal to a multiple of the original setting.

      This just might need to be documented. But maybe it could require a code change to allow.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            hill David Hill (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 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.