Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Won't Fix
-
1.1.6
-
None
-
1 UM and 4 PM. Upon configuration each pm was assigned one corresponding Dbroot using external storage
Description
After 1.1.6 upgrade, the movePmDbrootConfig failed. User was able to use unassign/assignpmdbroot commands as a work-around
-Restart of the modules themselves
-STOP of columnstore service from pm1
-Enable each module (pm3 only shown here)
mcsadmin> altersystem-enablemodule pm3
altersystem-enablemodule Mon Sep 17 12:22:48 2018
This command starts the processing of applications on a Module within the MariaDB ColumnStore System
Do you want to proceed: (y or n) [n]: y
Enabling Modules
Successful enable of Modules
Performance Module(s) Enabled, run movePmDbrootConfig or assignDbrootPmConfig to assign dbroots, if needed
- move dbroot from pm1 to pm3
mcsadmin> movePmDbrootConfig pm1 3 pm3
movepmdbrootconfig Mon Sep 17 12:23:47 2018
DBRoot IDs currently assigned to 'pm1' = 1, 3
DBRoot IDs currently assigned to 'pm3' =
DBroot IDs being moved, please wait...
DBRoot IDs newly assigned to 'pm1' = 1, 3
DBRoot IDs newly assigned to 'pm3' =
nothing in the logs point to any failures. So reason is unknown at this point.
