[MDEV-12512] Accurately report progress for ALTER TABLE...ALGORITHM=INPLACE - Jira

Details

Type: Bug
Status: Open (View Workflow)
Priority: Major
Resolution: Unresolved
Affects Version/s: 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
Fix Version/s: 10.5
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Labels:
- usability

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.

Attachments

Issue Links

relates to

MDEV-6812 Merge Kakao: Add global status variables which tell you the progress of inplace alter table and row log buffer usage

Closed

MDEV-9260 Improve progress report on on-line alter table

Open

MDEV-10509 Excessive InnoDB logging on release server

Closed

MDEV-16329 Engine-independent online ALTER TABLE

Closed

Activity

There are no comments yet on this issue.

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2017-04-17 00:44

Updated:: 2024-09-10 15:05

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server