percona-discussion team mailing list archive

[Xaprb <baron@xxxxxxxxx>]

Public bug reported:

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.

** Affects: percona-patches
     Importance: Undecided
         Status: New

-- 
Make deadlock search limits configurable
https://bugs.launchpad.net/bugs/335630
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona patches.

Status in Patches for MySQL by Percona: New

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.