Make deadlock search limits configurable
Bug #335630 reported by
Baron Schwartz
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
lock/lock0lock.c says
/* Restricts the length of search we will do in the waits-for
graph of transactions */
#define LOCK_MAX_
/* Restricts the recursion depth of the search we will do in the waits-for
graph of transactions */
#define LOCK_MAX_
I would like these to be configurable global variables. Can we also set the transaction's status so you see "checking for deadlock" in SHOW INNODB STATUS? That way, a user who increases these variables (or starts running into the deadlocks caused by them) will have a hint about what is happening.
Changed in percona-patches: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in percona-patches: | |
importance: | Low → Wishlist |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
no longer affects: | percona-patches |
To post a comment you must log in.
Since Percona Server has replaced percona-patches, I'm moving this Wishlist item over to Percona Server and marking as "Won't fix" for percona-patches