[MDEV-12512] Accurately report progress for ALTER TABLE...ALGORITHM=INPLACE Created: 2017-04-17  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1, 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.4, 10.5

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Unresolved Votes: 0
Labels: usability

Issue Links:
Relates
relates to MDEV-6812 Merge Kakao: Add global status variab... Closed
relates to MDEV-9260 Improve progress report on on-line al... Open
relates to MDEV-10509 Excessive InnoDB logging on release s... Closed
relates to MDEV-16329 Engine-independent online ALTER TABLE Closed

 Description   

As noted in MDEV-10509, MDEV-6812 introduced server-wide status variables for monitoring ALTER TABLE...ALGORITHM=INPLACE progress. That feels wrong, because there can be multiple ALTER TABLE being executed concurrently.

I think that we should report progress via the native MariaDB interface instead of spamming the error log.
In 10.2, the InnoDB code to report progress via a similar interface already exists. It only needs to be tied to the proper interface. For 10.1, I think that we can backport the progress reporting changes from 10.2.
Generated at Thu Feb 08 07:58:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.