provider library controlling WS limits
Bug #593441 reported by
Seppo Jaakola
This bug report is a duplicate of:
Bug #1270920: mysqld can't handle wsrep error on exceeding max writeset size.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL patches by Codership |
New
|
Low
|
Seppo Jaakola | ||
| 0.7 |
Won't Fix
|
Low
|
Seppo Jaakola | ||
| 0.8 |
Won't Fix
|
Low
|
Seppo Jaakola | ||
| 5.1 |
Won't Fix
|
Undecided
|
Seppo Jaakola | ||
| 5.5 |
New
|
Low
|
Seppo Jaakola | ||
Bug Description
According to blueprint: https:/
Check return code from wsrep calls pre_commit(), append_data(), append_query() and append_row_key(), and issue statement rollback, if write set limit was exceeded.
Drop obsolete WS limit variables; wsrep_max_ws_size and wsrep_max_ws_rows
Related branches
lp:~codership/codership-mysql/dev
(Merged)
| Changed in codership-mysql: | |
| importance: | Undecided → Low |
| assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
| assignee: | Seppo Jaakola (seppo-jaakola) → nobody |
Revision history for this message
| Alex Yurchenko (ayurchen) wrote | #1 |
To post a comment you must log in.
0.7 series is no longer supported