wsrep_max_ws_rows seems ineffective
Bug #1087614 reported by
Henrik Ingo
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
The option wsrep_max_ws_rows should limit max nr of rows a transaction can modify (and thus, replicate). Default is 128K. However, in Alex' own testing he deleted 3M rows without getting problems. Also on the mailing list people are hit by issues following running a large transaction.
As long as running a large transaction can lead to issues (ie forever), it would improve usability if this option actually enforces a max size on transactions. That way people would get a client side error instead of OOM and other issues.
note: also check wsrep_max_ws_size while at it.
Revision history for this message
| Philip Stoev (philip-stoev-f) wrote | #1 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #2 |
| Changed in codership-mysql: | |
| status: | New → Confirmed |
To post a comment you must log in.
wsrep_max_ws_size does not work for me, but wsrep_max_ws_rows does work.