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: upstream |
summary: |
- --super_read_only: to improve manual, or better, set --read_only on when - --super_read_only is used as command line option + set --read_only on when --super_read_only is used as command line option |
Roel Van de Paar (roel11) wrote : | #5 |
Compiling webscalesql is failing. Even after installing readline-devel (it's needed), I get this;
[ 96%] Building CXX object client/
/bzr/webscalesq
typedef struct _hist_entry {
^
In file included from /bzr/webscalesq
/usr/include/
typedef struct _hist_entry {
^
/bzr/webscalesq
} HIST_ENTRY;
^
/bzr/webscalesq
In file included from /bzr/webscalesq
/usr/include/
} HIST_ENTRY;
^
make[2]: *** [client/
make[1]: *** [client/
make: *** [all] Error 2
Any ideas?
Roel Van de Paar (roel11) wrote : | #6 |
If no ideas, I'll log upstream bug, which effectively halts progress on QA as there is another bug for which I need a compiled version also. Thanks
tags: | added: qablock |
Gary (pento) wrote : | #7 |
I was able to reproduce the behaviour in comment 5, compiling WebScaleSQL 5.6.23 on Ubuntu 14.04.1 LTS.
I fixed it by installing the libedit-dev package.
tags: | added: super-read-only |
Roel Van de Paar (roel11) wrote : | #8 |
tags: | removed: qablock |
This is fixed by Facebook patch by https:/
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/
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.