[MCOL-429] system status does not consider innodb recovery Created: 2016-12-02  Updated: 2023-10-26  Resolved: 2020-04-15

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.0.5
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: David Thompson (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: community


 Description   

In 1.0.5 after a failed transaction and crash recovery, restartSystem doesn't wait for mysql to restart properly.

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Thu Dec 1 01:13:30 2016

Module um1 ACTIVE Thu Dec 1 01:13:26 2016
Module pm1 ACTIVE Thu Dec 1 01:13:08 2016
Module pm2 ACTIVE Thu Dec 1 01:13:15 2016

Active Parent OAM Performance Module is 'pm1'

2016-12-01 1:12:16 140036511479552 [Note] InnoDB: FTS optimize thread exiting.
2016-12-01 1:12:16 140036570851072 [Note] InnoDB: Starting shutdown...
6 7 82016-12-01 1:13:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish
92016-12-01 1:14:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish
2016-12-01 1:15:16 140036570851072 [Note] InnoDB: Waiting for 1 active transactions to finish

 Comments   
Comment by Todd Stoffel (Inactive) [ 2020-04-15 ]

OAM is being deprecated and replaced by an enhanced API and the MaxScale orchestration project.

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