[MCOL-1486]  Internal errors: IDB-2034: At least one DBRoot required for that query is offline Created: 2018-06-20  Updated: 2023-10-26  Resolved: 2019-07-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.5
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

CentOS Linux 7.4



 Description   

Internal errors: IDB-2034: At least one DBRoot required for that query is offline

After upgrading mcs system was started successfully, mcsadmin getsystem status
did not return any failed state ,
however during queering
are received Internal errors IDB-2034: At least one DBRoot required for that query is offline.

The problem is that MCS started successfully and System is considered ACTIVE .
It seems that postConfigure script accepted invalid value of DBRoot IDs and Single Server installation finished with DBRootIDs assigned = 0 .

It would be expected to return Error for the invalid values of DBRoot IDs
or start MCS with an appropriate Internal Error System Status ,
otherwise system is considered ready for use but will return Internal errors .

MCS started successfully
 
[root@columnstore zdravelina.sokolovska]# mcsadmin start system
startsystem   Wed Jun 20 15:36:29 2018
startSystem command, 'columnstore' service is down, sending command to
start the 'columnstore' service on all modules
 
 
   System being started, please wait..........
   Successful start of System

mcsadmin getsystem status returns OK 
 
[root@columnstore bin]# mcsadmin getsystemi
getsysteminfo   Wed Jun 20 15:53:47 2018
 
System columnstore-1
 
System and Module statuses
 
Component     Status                       Last Status Change
------------  --------------------------   ------------------------
System        ACTIVE                       Wed Jun 20 15:37:39 2018
 
Module pm1    ACTIVE                       Wed Jun 20 15:37:30 2018
 
 
MariaDB ColumnStore Process statuses
 
Process             Module    Status            Last Status Change        Process ID
------------------  ------    ---------------   ------------------------  ----------
ProcessMonitor      pm1       ACTIVE            Wed Jun 20 15:36:53 2018        5238
ProcessManager      pm1       ACTIVE            Wed Jun 20 15:36:59 2018        5383
DBRMControllerNode  pm1       ACTIVE            Wed Jun 20 15:37:08 2018        5793
ServerMonitor       pm1       ACTIVE            Wed Jun 20 15:37:12 2018        5812
DBRMWorkerNode      pm1       ACTIVE            Wed Jun 20 15:37:12 2018        5854
DecomSvr            pm1       ACTIVE            Wed Jun 20 15:37:13 2018        5885
PrimProc            pm1       ACTIVE            Wed Jun 20 15:37:17 2018        5929
ExeMgr              pm1       ACTIVE            Wed Jun 20 15:37:21 2018        6000
WriteEngineServer   pm1       ACTIVE            Wed Jun 20 15:37:25 2018        6043
DDLProc             pm1       ACTIVE            Wed Jun 20 15:37:29 2018        6103
DMLProc             pm1       ACTIVE            Wed Jun 20 15:37:37 2018        6161
mysqld              pm1       ACTIVE            Wed Jun 20 15:37:02 2018        5686
 
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0

Errors received during  query processing
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.
ERROR 1815 (HY000) at line 1: Internal error: IDB-2034: At least one DBRoot required for that query is offline.

Jun 20 15:59:15 columnstore ExeMgr[13769]: 15.095567 |2147483668|0|0| D 16 CAL0041: Start SQL statement: select objectid,columnname from syscolumn where schema='tpcds_1' and tablename='date_dim' --columnRIDs/FE; ||
Jun 20 15:59:15 columnstore joblist[13769]: 15.107136 |0|0|0| D 05 CAL0000: dictionary forcing reload of columnstore.xml for dbRootConnectionMap
Jun 20 15:59:15 columnstore joblist[13769]: 15.107179 |0|0|0| D 05 CAL0000: dictionary forcing reload of columnstore.xml for dbRootConnectionMap
Jun 20 15:59:15 columnstore joblist[13769]: 15.130471 |0|0|0| D 05 CAL0000: dictionary still not in dbRootConnectionMap
Jun 20 15:59:15 columnstore joblist[13769]: 15.130574 |2147483668|0|0| C 05 CAL0000: IDB-2034: At least one DBRoot required for that query is offline.
Jun 20 15:59:15 columnstore joblist[13769]: 15.130646 |0|0|0| D 05 CAL0000: dictionary still not in dbRootConnectionMap
Jun 20 15:59:15 columnstore joblist[13769]: 15.130726 |2147483668|0|0| C 05 CAL0000: IDB-2034: At least one DBRoot required for that query is offline.
Jun 20 15:59:15 columnstore ExeMgr[13769]: 15.133149 |2147483668|0|0| D 16 CAL0042: End SQL statement

It's found that installation was done with DBRootIDs assigned  = 0 
after not valid value was being passed to DBRoot IDs
 
[root@columnstore bin]# mcsadmin getModuleConfig
getmoduleconfig   Wed Jun 20 16:06:29 2018
 
Module Name Configuration
 
Module 'pm1' Configuration information
 
ModuleType = pm
ModuleDesc = Performance Module #1
ModuleIPAdd NIC ID 1 = 127.0.0.1
ModuleHostName NIC ID 1 = localhost
DBRootIDs assigned  = 0
 

Select the type of System Server install [1=single, 2=multi] (1) > 1
 
Performing the Single Server Install.
Enter System Name (columnstore-1) > columnstore-1
 
===== Storage Configuration = internal =====
 
 
Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) > pm1
 
 
===== Performing Configuration Setup and MariaDB ColumnStore Startup =====
 
NOTE: Using previous configuration setting for 'NumBlocksPct' = 50%
      Using previous configuration setting for 'TotalUmMemory' = 25%
 
Running the MariaDB ColumnStore setup scripts
 
post-mysqld-install Successfully Completed



 Comments   
Comment by David Hill (Inactive) [ 2018-06-20 ]

Thanks for reporting this issue... you are correct, there should have been error checking around the entry of the dbroot ID to make sure it was a valid numerical value

Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) > pm1

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