Implement limit for undo segment size

Bug #592379 reported by Peter Zaitsev on 2010-06-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Wishlist
Unassigned

Bug Description

Allow to limit undo segment size to prevent run away main tablespace and general run away transactions.
If we're out of undo space transactions causing modifications which can't get undo slot record allocated should fail.

Vadim Tkachenko (vadim-tk) wrote :

Along with that we can implement to store undo area in separate file

Changed in percona-server:
status: New → Confirmed
importance: Undecided → Wishlist
Peter Zaitsev (pz-percona) wrote :

There are actually 2 ways to implement it and we might make it configurable. One to have transaction which performs update to fail, another is to kill transaction which is oldest (and preventing purge from process). In the former case we probably should kill it some time before the hard limit is reached.

Second approach can be better for a lot of multi user system which prevent application which started run away transaction from making the whole system non functional. I think just to kill such transaction instead of making system to be effectively read only is preferable.

Stewart Smith (stewart) on 2011-05-25
Changed in percona-server:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers