[MCOL-3810] mysqld restarted 2 or 3 times after postConfigure is completed Created: 2020-02-19  Updated: 2023-11-27  Resolved: 2020-02-25

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

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

Attachments: Text File debug.log     Text File debug_2pm_combo_with_replication.log    

 Description   

Build tested: 1.4.3-1 Source

engine commit:
1a65d34

From the debug.log file, mysql's PID changed few times. If the user execute a SQL script immediately after postConfigure, and if mysqld happens to be down at that moment, the following error returned:

ERROR 2013 (HY000) at line 4: Lost connection to MySQL server during query

restarting the system (pam restartsystem) does not have this issue.
1.4.2-1 also does not have this issue.

I am not sure why mysqld needs to restart. Could this be a timing issue relating to MCOL-3718?

 Comments   
Comment by Daniel Lee (Inactive) [ 2020-02-21 ]

Attached debug.log

When the ColumnStore starts, mysql's PID changed twice, has a total of three different PIDs

[root@localhost columnstore]# cat debug.log |grep mysqld
Feb 21 21:52:17 localhost ProcessMonitor[13092]: 17.966621 |0|0|0| D 18 CAL0000: mysqld Monitoring Thread started ..
Feb 21 21:52:50 localhost ProcessMonitor[13092]: 50.117226 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Process pm1/mysqld State = ACTIVE
Feb 21 21:52:50 localhost ProcessMonitor[13092]: 50.117495 |0|0|0| D 18 CAL0000: statusControl: Set Process pm1/mysqld State = ACTIVE PID = 13331
Feb 21 21:52:51 localhost ProcessMonitor[13092]: 51.298251 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Process pm1/mysqld State = ACTIVE
Feb 21 21:52:51 localhost ProcessMonitor[13092]: 51.298388 |0|0|0| D 18 CAL0000: statusControl: Set Process pm1/mysqld State = ACTIVE PID = 13331
Feb 21 21:53:01 localhost ProcessMonitor[13092]: 01.413044 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Process pm1/mysqld State = ACTIVE
Feb 21 21:53:01 localhost ProcessMonitor[13092]: 01.413158 |0|0|0| D 18 CAL0000: statusControl: Set Process pm1/mysqld State = ACTIVE PID = 13331
Feb 21 21:53:06 localhost ProcessMonitor[13092]: 06.598068 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Process pm1/mysqld State = ACTIVE
Feb 21 21:53:06 localhost ProcessMonitor[13092]: 06.598148 |0|0|0| D 18 CAL0000: statusControl: Set Process pm1/mysqld State = ACTIVE PID = 13755
Feb 21 21:53:52 localhost ProcessMonitor[13092]: 52.839931 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Process pm1/mysqld State = ACTIVE
Feb 21 21:53:52 localhost ProcessMonitor[13092]: 52.840338 |0|0|0| D 18 CAL0000: statusControl: Set Process pm1/mysqld State = ACTIVE PID = 14389

Comment by Daniel Lee (Inactive) [ 2020-02-25 ]

Build verified: 1.4.3-1 BB special build (20200225)

Engine commit: 20247bc

One mysqld restart is expected. ColumnStore now starts correctly. 2pm combo replication also configured correct. Replication is work.

Work along with development team on this tickets.

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