Skip to:

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

handle_fatal_signal (sig=11) in ha_tokudb::write_row

Description

Leads to:

In 5.7.21 it gives:

 Also in 5.7 trunk (not George's tree), it gives the same error as per George. George's tree which produces this crash (i.e. the new 23-25 release);

Environment

None

Smart Checklist

Activity

Show:

George Lorch November 29, 2018 at 4:54 AM
Edited

Peter Schwaller November 27, 2018 at 1:09 PM

Deferring from 8.0 as it is "not very serious" and affects 5.7 (and 5.6) as well.

roel.vandepaar November 21, 2018 at 12:07 AM

Understood! thank you

George Lorch November 20, 2018 at 10:56 PM

This is not introduced to TokuDB by reverting two commits in MyRocks.  It is likely a regression introduced by https://github.com/percona/percona-server/commit/23c0a7280150636dc3f4d12e01748f31b2be06a2  and not very 'serious' in that it requires an auto increment rollover on a TEMPORARY TokuDB table only during an INSERT IGNORE. 

roel.vandepaar November 20, 2018 at 10:45 PM
Edited

Issue needs eval before release of RM-417. If George is ok with it, then we can release RM-417. To me this looks serious, except for the hex component.

Done

Details

Assignee

Reporter

Labels

Time tracking

2h 35m logged

Components

Fix versions

Affects versions

Priority

Smart Checklist

Created November 20, 2018 at 10:38 PM
Updated March 6, 2024 at 12:39 PM
Resolved November 30, 2018 at 3:54 PM