innodb_log_block_size mismatch between log files and current configuration is diagnosed as "No valid checkpoints found"
Bug #1155156 reported by
Laurynas Biveinis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Medium
|
Unassigned | |||
5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
PS 5.5 stores the non-default innodb_
summary: |
- Upgrade from non-default innodb_log_block_size to 5.6 should work + Server should diagnose non-standard innodb_log_block_size on 5.6 upgrade |
tags: | added: i64171 |
summary: |
- Verify innodb_log_block_size mismatch diagnostics + innodb_log_block_size mismatch between log files and current + configuration is diagnosed as "No valid checkpoints found" |
To post a comment you must log in.
Nevermind, we are porting the feature forward.