[DOC] wsrep_max_ws_rows is enabled again, update the documentation
Bug #1638034 reported by
Miguel Angel Nieto
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.6 |
Fix Released
|
Undecided
|
Hrvoje Matijakovic | |||
| 5.7 |
Fix Released
|
Undecided
|
Hrvoje Matijakovic | |||
Bug Description
Latest Percona XtraDB Cluster 5.6.32-25.17 version uses Galera Replication library 3.17 that enables once again the wsrep_max_ws_rows variable, with a default value of 0 (no limit).
Please, update the documentation.
| description: | updated |
Revision history for this message
| Przemek (pmalkowski) wrote | #1 |
| Changed in percona-xtradb-cluster: | |
| status: | New → Confirmed |
| tags: | added: doc |
| summary: |
- wsrep_max_ws_rows is enabled again, update the documentation + [DOC] wsrep_max_ws_rows is enabled again, update the documentation |
| Changed in percona-xtradb-cluster: | |
| assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
Revision history for this message
| Hrvoje Matijakovic (hrvojem) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
Indeed:
http://
and in
http://
"The wsrep_max_ws_rows variable has been fixed and can be used to set the maximum number of rows a transaction can update, delete or insert. The new default value is 0, meaning no limit."
also for reference:
https:/