Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Setting tokudb_last_lock_timeout via command line or cli can cause server to abort when an actual timeout occurs

Description

sql:

Running the above sql
crashes the server:

gdb:

Reproduced with 5.7 (635b624d8acf5e9812537884efed332a797cad0e)

Environment

None

Smart Checklist

Activity

George Lorch November 2, 2018 at 9:55 PM
Edited

George Lorch November 2, 2018 at 4:13 PM

This actually has nothing to do with either XA or temp tables.  It is due to the memory management around the string sysvar tokudb_last_lock_timeout which is not an 'input' variable but is used to relay textual information about the last lock wait timeout to the user.  This really should not be 'settable' via either the command line or the cli.  See https://bugs.mysql.com/bug.php?id=71759

Done

Details

Assignee

Reporter

Time tracking

3h 30m logged

Components

Fix versions

Affects versions

Priority

Smart Checklist

Created October 17, 2018 at 4:37 PM
Updated March 6, 2024 at 12:45 PM
Resolved November 6, 2018 at 8:22 PM