[MCOL-5065] mcssystemready() is returning inaccurate value Created: 2022-04-28  Updated: 2022-05-23  Resolved: 2022-05-23

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: 6.4.1

Type: Bug Priority: Major
Reporter: Todd Stoffel (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Attachments: Text File mariadb-error.log    
Issue Links:
Blocks
blocks MCOL-5064 CS pods taking 2 min to start - discu... Closed

 Description   

[root@mcs1 /]# mariadb -e "SELECT mcssystemready()"
+------------------+
| mcssystemready() |
+------------------+
|                1 |
+------------------+
[root@mcs1 /]# mariadb -e "SELECT * FROM test.t1"
+------+
| id   |
+------+
|   99 |
|   77 |
+------+
[root@mcs1 /]# mcsShutdown
{
  "timestamp": "2022-04-28 19:10:59.906225",
  "mcs1": {
    "timestamp": "2022-04-28 19:11:09.419228"
  },
  "mcs2": {
    "timestamp": "2022-04-28 19:11:12.840278"
  },
  "mcs3": {
    "timestamp": "2022-04-28 19:11:16.240289"
  }
}
[root@mcs1 /]# mariadb -e "SELECT mcssystemready()"
+------------------+
| mcssystemready() |
+------------------+
|                1 |
+------------------+
[root@mcs1 /]# mariadb -e "SELECT * FROM test.t1"
ERROR 1815 (HY000) at line 1: Internal error: DBRM is not responding. Cannot accept queries



 Comments   
Comment by alexey vorovich (Inactive) [ 2022-04-29 ]

Ok.. i will ignore for the API Key issue.

David.Hall please review and lets move to test

Comment by David Hall (Inactive) [ 2022-05-02 ]

QA: The function works correctly if Columnstore is up but not yet ready. It returns true (when it should be false) if columnstore is down or in the very early stages of being started. This patch should fix it to work in all cases.

Comment by Daniel Lee (Inactive) [ 2022-05-23 ]

Build verified: Drone #4472

In a script to check for mcssystemready() return value before and after mcsShutdown and mcsStart. Repeated the test many times and returned values were correct.

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