Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2
-
None
Description
MariaDB [test]> select @@version;
|
+--------------------------+
|
| @@version |
|
+--------------------------+
|
| 10.2.3-MariaDB-debug-log |
|
+--------------------------+
|
1 row in set (0.00 sec)
|
|
|
MariaDB [test]> create table t1(i int)engine=innodb;
|
Query OK, 0 rows affected (0.05 sec)
|
|
|
MariaDB [test]> SET GLOBAL innodb_disallow_writes=ON;
|
Query OK, 0 rows affected (0.00 sec)
|
|
|
MariaDB [test]> insert into t1 values(1);
|
Query OK, 1 row affected (0.01 sec)
|
|
|
MariaDB [test]> select * from t1;
|
+------+
|
| i |
|
+------+
|
| 1 |
|
+------+
|
1 row in set (0.00 sec)
|
Test case: galera.galera_var_innodb_disallow_writes
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Open
-
Activity
commit 5a9c63ab5535778839de74dfd16837de8b1f7f5e
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Thu Feb 1 13:35:03 2018 +0200
MDEV-10949: innodb_disallow_writes does not work as expected
Test seems to pass fine.
As noted in MDEV-11035 and MDEV-15770, something in the Galera rsync snapshot transfer is not working correctly. (The reason why the parameter innodb_disallow_writes exists is the rsync snapshot transfer.)
jplindst Reopening as this issue has re-surfaced. I noticed that 10.2-HEAD is still affected.