[MCOL-4973] Update MariaDB Columnstore to 6.2.2, mcsStatus "cluster_mode" is null Created: 2022-01-26  Updated: 2022-04-07  Resolved: 2022-02-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: cmapi
Affects Version/s: cmapi-1.6
Fix Version/s: cmapi-1.6.2

Type: Bug Priority: Major
Reporter: Edward Stoever Assignee: Alan Mologorsky
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Problem/Incident
causes MCOL-4954 Add support for new DBRM socket bytes... Closed

 Description   

As seen in CS0373526. I have replicated this:

root@cs1:~$ mcsStatus
 
{
 
  "timestamp": "2022-01-26 14:07:16.909579",
 
  "192.168.20.133": {
 
    "timestamp": "2022-01-26 14:07:16.917042",
 
    "uptime": 286,
 
    "dbrm_mode": "master",
 
    "cluster_mode": null,
 
    "dbroots": [
 
      "1"

It is possible this is due to the update from 10.5 to 10.6 or it could be like this on 10.6 on a general install.

 Comments   
Comment by Allen Lee (Inactive) [ 2022-02-10 ]

once cluster_mode got null, I couldn't run mcsReadWrite or mcsReadonly due to the following errors:

[root@mcs2 ~]# mcsReadWrite
 
{
 
  "error": "got an error setting cluster to readwrite: 422 Client Error: Unprocessable Entity for url: https://192.168.254.8:8640/cmapi/0.4.0/node/config"
 
}
 
[root@mcs1 ~]# mcsReadOnly
 
{
 
  "error": "got an error setting cluster to readonly: 422 Client Error: Unprocessable Entity for url: https://192.168.254.8:8640/cmapi/0.4.0/node/config"
 
}

But, the cluster is still functional, which I can read/write/create table.

Comment by Alan Mologorsky [ 2022-02-10 ]

Fixed in MCOL-4954

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