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

removedbroot not working after redistributedata start remove - dbroot #3 is not empty

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.2.5
    • Fix Version/s: N/A
    • Component/s: oam
    • Labels:
      None

      Description

      Customer trying to remove a pm and a dbroot from their system and getting the error that dbroot is not empty even though they did a redistributedata start remove 3.

      Maybe the procedure on how Im having them do it is incorrect.

      here is the full process i ran. it seems to still have failed even though it allowed me to remove the module it says the dbroot has data.

      mcsadmin> suspendDatabaseWrites
      suspenddatabasewrites Fri Dec 20 16:32:34 2019

      This command suspends the DDL/DML writes to the MariaDB ColumnStore Database
      Do you want to proceed: (y or n) [n]: y

      Suspend MariaDB Columnstore Database Writes Request successfully completed
      mcsadmin> redistributedata start remove 3
      redistributedata Fri Dec 20 16:32:47 2019
      redistributeData START
      Source dbroots: 1 2 3
      Destination dbroots: 1 2 3

      WriteEngineServer returned status 1: Cleared.
      WriteEngineServer returned status 2: Redistribute is started.
      mcsadmin> redistributedata status
      redistributedata Fri Dec 20 16:32:55 2019
      WriteEngineServer returned status 3: Redistribute is finished.
      0 success, 0 skipped, 0 failed.
      Total time: 3 seconds.

      mcsadmin> resumeDatabaseWrites
      resumedatabasewrites Fri Dec 20 16:33:37 2019

      This command resumes the DDL/DML writes to the MariaDB ColumnStore Database
      Do you want to proceed: (y or n) [n]: y

      Resume MariaDB ColumnStore Database Writes Request successfully completed
      mcsadmin> stopsystem y
      stopsystem Fri Dec 20 16:33:42 2019

      This command stops the processing of applications on all Modules within the MariaDB ColumnStore System

      Checking for active transactions

      System being stopped now...
      Successful stop of System

      mcsadmin> unassignDbrootPmConfig 3 pm3
      unassigndbrootpmconfig Fri Dec 20 16:34:19 2019

      DBRoot IDs assigned to 'pm3' = 3
      Changes being applied...
      DBRoot IDs unassigned from 'pm3' = 3
      DBRoot IDs assigned to 'pm3' =

      Successfully Unassigned DBRoots

      mcsadmin> removemodule pm3
      removemodule Fri Dec 20 16:34:27 2019

      !!!!! DESTRUCTIVE COMMAND !!!!!

      This command removes module(s) from the MariaDB ColumnStore System
      Do you want to proceed: (y or n) [n]: y

      Removing Module(s) pm3, please wait...

      Remove Module successfully completed

      mcsadmin> startsystem
      startsystem Fri Dec 20 16:34:39 2019

      System being started, please wait...
      Successful start of System

      mcsadmin> removedbroot 3
      removedbroot Fri Dec 20 16:35:50 2019

      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      BRMShmImpl::BRMShmImpl(): retrying on size==0
      No such file or directory
      ERROR: isDBRootEmpty API error, dbroot #3 :No such file or directory
      ERROR: Failed remove, dbroot #3 is not empty

            • removeDbroot Failed: API Failure return in removeDbroot API

      Error logs
      ==> mcsadmin.log <==
      Fri Dec 20 16:35:50 2019: removedbroot 3

      ==> crit.log <==
      Dec 20 16:35:55 ip-172-22-0-100 controllernode[28064]: 55.974902 |0|0|0| C 29 CAL0000: BRMShmImpl::BRMShmImpl(): retrying on size==0

      ==> debug.log <==
      Dec 20 16:35:55 ip-172-22-0-100 controllernode[28064]: 55.974902 |0|0|0| C 29 CAL0000: BRMShmImpl::BRMShmImpl(): retrying on size==0

      ==> err.log <==
      Dec 20 16:35:55 ip-172-22-0-100 controllernode[28064]: 55.974902 |0|0|0| C 29 CAL0000: BRMShmImpl::BRMShmImpl(): retrying on size==0

      ==> info.log <==
      Dec 20 16:35:55 ip-172-22-0-100 controllernode[28064]: 55.974902 |0|0|0| C 29 CAL0000: BRMShmImpl::BRMShmImpl(): retrying on size==0

      ==> warning.log <==
      Dec 20 16:35:55 ip-172-22-0-100 controllernode[28064]: 55.974902 |0|0|0| C 29 CAL0000: BRMShmImpl::BRMShmImpl(): retrying on size==0

        Attachments

          Activity

            People

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