Test innodb.percona_changed_page_bmp_crash is unstable
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
Low
|
Laurynas Biveinis |
Bug Description
On 5.5 trunk:
innodb.
Test ended at 2016-08-11 18:28:33
CURRENT_TEST: innodb.
--- /mnt/workspace/
+++ /mnt/workspace/
@@ -31,5 +31,4 @@
INSERT INTO t1 VALUES (1),(2)
ib_modified_log_1
ib_modified_log_2
-ib_modified_log_3
DROP TABLE t1, t2;
mysqltest: Result length mismatch
safe_process[
One way this can happen is when ib_modified_log_2* is zero-sized at the time of the last server restart. Then it would get reused instead of rotated. There is no protection against it being zero sized as there is no write workload before the resize, the only way it can get bitmap data written is by crash recovery, but the crashed instance might have written everything already.
tags: | added: bitmap ci |
https:/ /github. com/percona/ percona- server/ pull/819 /github. com/percona/ percona- server/ pull/820 /github. com/percona/ percona- server/ pull/821
https:/
https:/