[MCOL-1732] movePmDbrootConfig on external disk fails Created: 2018-09-20  Updated: 2023-10-26  Resolved: 2020-04-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.6
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: David Hill (Inactive) Assignee: Ben Thompson (Inactive)
Resolution: Won't Fix Votes: 2
Labels: None
Environment:

1 UM and 4 PM. Upon configuration each pm was assigned one corresponding Dbroot using external storage

Issue Links:
Relates
relates to MCOL-1976 Amazon AMI with EBS - movepmdbrootcon... Closed
relates to MCOL-3308 Cannot move DBRoot to resurrected PM ... Closed

 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.

 Comments   
Comment by David Hill (Inactive) [ 2019-04-18 ]

This BUG has nothing to do with PanFS. I was able to reproduce on a normal Amazon system using EBS storage like EXT4 fstab storage. Also problem occurs on normal Amazon EBS configuration.

MCOL-1976

Comment by David Hill (Inactive) [ 2019-06-03 ]

I worked with a customer today that has an amazon system where we ran into this issue, the move command failing.

https://support.mariadb.com/view.php?id=28646

This has been an open bug for awhile and we need to get some priority on getting it fixed.

I believe this BUG is tie to the same problem. This failed because the auto move failed

https://jira.mariadb.org/browse/MCOL-3308

Comment by David Hill (Inactive) [ 2019-06-06 ]

This issue is happening on other systems, so even though it was opened initially for a PANFS customer, its not related...

Comment by David Hill (Inactive) [ 2019-09-19 ]

Another customer reported issue

Comment by David Hill (Inactive) [ 2019-11-13 ]

Customer is requesting that is fixed in 1.2, issue 31062

Comment by Todd Stoffel (Inactive) [ 2020-04-15 ]

OAM is being deprecated and replaced by an enhanced API and the MaxScale orchestration project.

Generated at Thu Feb 08 02:30:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.