Make deadlock search limits configurable

Bug #335630 reported by Baron Schwartz
2
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_N_STEPS_IN_DEADLOCK_CHECK 1000000

/* Restricts the recursion depth of the search we will do in the waits-for
graph of transactions */
#define LOCK_MAX_DEPTH_IN_DEADLOCK_CHECK 200

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)
Revision history for this message
Stewart Smith (stewart) wrote :

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

Changed in percona-server:
status: New → Triaged
importance: Undecided → Wishlist
Changed in percona-patches:
status: Confirmed → Won't Fix
no longer affects: percona-patches
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2293

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.