set --read_only on when --super_read_only is used as command line option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
* Start PS mysqld with --super_read_only
* In CLI;
=======
mysql> show global variables like 'super_
+------
| Variable_name | Value |
+------
| super_read_only | ON |
+------
1 row in set (0.00 sec)
+------
| Variable_name | Value |
+------
| read_only | OFF | <------
+------
1 row in set (0.00 sec)
mysql> SET GLOBAL super_read_
Query OK, 0 rows affected (0.00 sec)
mysql> show global variables like 'super_
+------
| Variable_name | Value |
+------
| super_read_only | OFF |
+------
1 row in set (0.00 sec)
+------
| Variable_name | Value |
+------
| read_only | OFF |
+------
1 row in set (0.00 sec)
mysql> SET GLOBAL super_read_only=ON;
Query OK, 0 rows affected (0.00 sec)
mysql> show global variables like 'super_
+------
| Variable_name | Value |
+------
| super_read_only | ON |
+------
1 row in set (0.00 sec)
+------
| Variable_name | Value |
+------
| read_only | ON |
+------
1 row in set (0.00 sec)
=======
Note (!) marker. Either (imho best) the read_only should be ON when --super_read_only was used as a startup paramenter, or the manual should be improved to make it clear that if --super_read_only is used as a command line option, that it does not automatically enable --read_only.
Manual is here;
http://
description: | updated |
description: | updated |
tags: | added: qablock |
tags: | added: super-read-only |
tags: | removed: qablock |
Must be an upstream bug, please test WebScaleSQL and report it there (https:/ /github. com/webscalesql /webscalesql- 5.6/issues).
This needs fixing as suggested, not documenting the current behavior.