[MDEV-11027] InnoDB log recovery is too noisy - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.0(EOL)
Fix Version/s: 5.5.55, 10.0.30, 10.1.22, 10.2.5
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
Labels:
- upstream

Sprint:
5.5.55, 10.2.5-1

Description

https://bugs.mysql.com/bug.php?id=78844

Attachments

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

jan.opt
0.1 kB
2017-02-21 09:40
jan.test
0.9 kB
2017-02-21 09:40

Issue Links

causes

MDEV-13814 Extra logging when innodb_log_archive=ON ( [Note] InnoDB: Read redo log up to LSN=...)

Closed

MDEV-14174 crash on start with innodb-track-changed-pages

Closed

relates to

MDEV-6456 No progress indication for "Reading tablespace information from the .ibd files"

Closed

MDEV-10509 Excessive InnoDB logging on release server

Closed

MDEV-12103 Reduce the time of looking for MLOG_CHECKPOINT during crash recovery

Closed

MDEV-14705 systemd: EXTEND_TIMEOUT_USEC= to avoid startup and shutdown timeouts

Closed

MDEV-29911 InnoDB recovery and mariadb-backup --prepare fail to report detailed progress

Closed

(2 relates to)

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Jan Lindström (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2016-10-11 10:07

Updated:: 2022-10-30 08:56

Resolved:: 2017-03-09 07:00

Git Integration

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