[DOC] Make clear that wsrep_max_ws_rows has no effect
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership |
New
|
Undecided
|
Unassigned | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Alexey Zhebel | |||
5.6 |
Invalid
|
Undecided
|
Alexey Zhebel |
Bug Description
The wsrep_max_ws_rows variable does not work, as explained in:
https:/
https:/
https:/
and it is unclear if it's implementation will ever be finished.
Yet the documentation is now misleading the users:
https:/
https:/
http://
We should make it very clear that such variable was added as intention but never really made to work.
A quick test:
percona1 mysql> select @@version,
+------
| @@version | @@version_comment |
+------
| 5.6.30-76.3-56 | Percona XtraDB Cluster (GPL), Release rel76.3, Revision aa929cb, WSREP version 25.16, wsrep_25.16 |
+------
1 row in set (0.00 sec)
percona1 mysql> show status like 'ws%status';
+------
| Variable_name | Value |
+------
| wsrep_cluster_
+------
1 row in set (0.00 sec)
percona1 mysql> select @@wsrep_
+------
| @@wsrep_max_ws_rows |
+------
| 131072 |
+------
1 row in set (0.00 sec)
percona1 mysql> update t2 set a=a+1;
Query OK, 599040 rows affected (44.44 sec)
Rows matched: 599040 Changed: 599040 Warnings: 0
Changed in percona-xtradb-cluster: | |
status: | New → Confirmed |
This was fixed according to https:/ /github. com/codership/ mysql-wsrep/ issues/ 257