[MDEV-11167] InnoDB: Warning: using a partial-field key prefix in search, results in assertion failure or "Can't find record" error - Jira

Elena Stepanova created issue - 2016-10-28 15:22

Elena Stepanova made changes - 2017-04-20 17:52

Field	Original Value	New Value
Affects Version/s		10.1 [ 16100 ]

Elena Stepanova made changes - 2017-05-22 11:34

Affects Version/s

10.2 [ 14601 ]

Elena Stepanova made changes - 2017-09-18 22:49

Link

This issue duplicates ~~MDEV-13838~~ [ ~~MDEV-13838~~ ]

Elena Stepanova made changes - 2017-09-18 22:49

Component/s		Storage Engine - InnoDB [ 10129 ]
Fix Version/s		N/A [ 14700 ]
Resolution		Duplicate [ 3 ]
Status	Open [ 1 ]	Closed [ 6 ]

Elena Stepanova made changes - 2017-10-25 11:17

Resolution	Duplicate [ 3 ]
Status	Closed [ 6 ]	Stalled [ 10000 ]

Elena Stepanova made changes - 2017-10-29 12:26

Description

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}

Elena Stepanova made changes - 2017-10-29 17:00

Description

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

Elena Stepanova made changes - 2017-10-29 17:01

Description

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2 and 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

Elena Stepanova made changes - 2017-10-29 17:34

Description

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2 and 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2 and 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

{code:sql|title=Crash in all 10.x}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t (f1 INT, f2 INT, f3 INT, KEY(f2))
ENGINE=InnoDB
PARTITION BY RANGE (f1) (
  PARTITION p0 VALUES LESS THAN (1),
  PARTITION p1 VALUES LESS THAN (128),
  PARTITION p2 VALUES LESS THAN MAXVALUE
);
INSERT INTO t VALUES (NULL,0,24),(NULL,0,0),(0,21,0),(4,0,NULL),(1,8,2),(5,66,0);

CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = 1;

# Cleanup
DROP VIEW v;
DROP TABLE t;
{code}

Elena Stepanova made changes - 2017-10-29 18:10

Description

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.2 and 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

{code:sql|title=Crash in all 10.x}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t (f1 INT, f2 INT, f3 INT, KEY(f2))
ENGINE=InnoDB
PARTITION BY RANGE (f1) (
  PARTITION p0 VALUES LESS THAN (1),
  PARTITION p1 VALUES LESS THAN (128),
  PARTITION p2 VALUES LESS THAN MAXVALUE
);
INSERT INTO t VALUES (NULL,0,24),(NULL,0,0),(0,21,0),(4,0,NULL),(1,8,2),(5,66,0);

CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = 1;

# Cleanup
DROP VIEW v;
DROP TABLE t;
{code}

http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio

{noformat}
2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
R6010
- abort() has been called
161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=501
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 196100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x5e451f37c8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477]
mysqld.exe!raise()[winsig.c:594]
mysqld.exe!abort()[abort.c:82]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2371]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2506]
mysqld.exe!do_select()[sql_select.cc:17565]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084]
mysqld.exe!JOIN::exec()[sql_select.cc:2375]
mysqld.exe!mysql_select()[sql_select.cc:3310]
mysqld.exe!mysql_multi_update()[sql_update.cc:1601]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3373]
mysqld.exe!mysql_parse()[sql_parse.cc:6570]
mysqld.exe!dispatch_command()[sql_parse.cc:1312]
mysqld.exe!do_command()[sql_parse.cc:999]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
KERNEL32.DLL!VirtualUnlock()
ntdll.dll!RtlGetActiveActivationContext()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 /* QUERY_NO 2740 CON_ID 13 */
Connection ID (thread ID): 13
Status: NOT_KILLED
{noformat}

{code:sql|title=Crash in 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t1 (a INT) ENGINE=InnoDB;
CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2;
CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION;

INSERT INTO t1 VALUES (1),(2);
INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4);
UPDATE v SET a = NULL ORDER BY a, b;

DROP TABLE t1, t2;
{code}
{code:sql|title=Crash in 10.0, 10.2 and 10.3}
--source include/have_innodb.inc
--source include/have_partition.inc

SET GLOBAL innodb_stats_persistent= ON;

CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2;
INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66);
CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = NULL;
{code}

{code:sql|title=Crash in all 10.x}
--source include/have_innodb.inc
--source include/have_partition.inc

CREATE TABLE t (f1 INT, f2 INT, f3 INT, KEY(f2))
ENGINE=InnoDB
PARTITION BY RANGE (f1) (
  PARTITION p0 VALUES LESS THAN (1),
  PARTITION p1 VALUES LESS THAN (128),
  PARTITION p2 VALUES LESS THAN MAXVALUE
);
INSERT INTO t VALUES (NULL,0,24),(NULL,0,0),(0,21,0),(4,0,NULL),(1,8,2),(5,66,0);

CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION;
UPDATE v SET f2 = 1;

# Cleanup
DROP VIEW v;
DROP TABLE t;
{code}

Elena Stepanova made changes - 2017-10-29 18:11

Summary

[Draft] Assertion failure in thread 124 in file row0sel.cc line 2500 InnoDB: Failing assertion: 0

InnoDB: Failing assertion: 0 in file row0sel.cc line 2498

Elena Stepanova made changes - 2017-10-29 18:16

Component/s		Partitioning [ 10802 ]
Component/s		Views [ 10111 ]
Fix Version/s		10.0 [ 16000 ]
Fix Version/s		10.1 [ 16100 ]
Fix Version/s		10.2 [ 14601 ]
Fix Version/s	N/A [ 14700 ]
Description	http://buildbot.askmonty.org/buildbot/builders/win-rqg-se/builds/2801/steps/rqg_crash_tests/logs/stdio {noformat} 2016-10-27 01:34:29 7c InnoDB: Assertion failure in thread 124 in file row0sel.cc line 2500 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. R6010 - abort() has been called 161027 4:34:29 [ERROR] mysqld got exception 0x80000003 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.0.28-MariaDB-debug key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=7 max_threads=501 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)max_threads = 196100 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x5e451f37c8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... mysqld.exe!my_sigabrt_handler()[my_thr_init.c:477] mysqld.exe!raise()[winsig.c:594] mysqld.exe!abort()[abort.c:82] mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2500] mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9083] mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:9668] mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624] mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5029] mysqld.exe!handler::ha_rnd_pos()[handler.cc:2624] mysqld.exe!multi_update::do_updates()[sql_update.cc:2371] mysqld.exe!multi_update::send_eof()[sql_update.cc:2506] mysqld.exe!do_select()[sql_select.cc:17565] mysqld.exe!JOIN::exec_inner()[sql_select.cc:3084] mysqld.exe!JOIN::exec()[sql_select.cc:2375] mysqld.exe!mysql_select()[sql_select.cc:3310] mysqld.exe!mysql_multi_update()[sql_update.cc:1601] mysqld.exe!mysql_execute_command()[sql_parse.cc:3373] mysqld.exe!mysql_parse()[sql_parse.cc:6570] mysqld.exe!dispatch_command()[sql_parse.cc:1312] mysqld.exe!do_command()[sql_parse.cc:999] mysqld.exe!threadpool_process_request()[threadpool_common.cc:271] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] KERNEL32.DLL!VirtualUnlock() ntdll.dll!RtlGetActiveActivationContext() ntdll.dll!RtlFreeUnicodeString() KERNEL32.DLL!BaseThreadInitThunk() ntdll.dll!RtlUserThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x5e451f7f00): UPDATE view3 SET field2 = 'up', field4 = 'ok' ORDER BY field1, field2, field3, field4 LIMIT 1 / QUERY_NO 2740 CON_ID 13 / Connection ID (thread ID): 13 Status: NOT_KILLED {noformat} {code:sql\|title=Crash in 10.3} --source include/have_innodb.inc --source include/have_partition.inc CREATE TABLE t1 (a INT) ENGINE=InnoDB; CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2; CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION; INSERT INTO t1 VALUES (1),(2); INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4); UPDATE v SET a = NULL ORDER BY a, b; DROP TABLE t1, t2; {code} {code:sql\|title=Crash in 10.0, 10.2 and 10.3} --source include/have_innodb.inc --source include/have_partition.inc SET GLOBAL innodb_stats_persistent= ON; CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2; INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66); CREATE ALGORITHM=MERGE VIEW v AS SELECT t1. FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION; UPDATE v SET f2 = NULL; {code} {code:sql\|title=Crash in all 10.x} --source include/have_innodb.inc --source include/have_partition.inc CREATE TABLE t (f1 INT, f2 INT, f3 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY RANGE (f1) ( PARTITION p0 VALUES LESS THAN (1), PARTITION p1 VALUES LESS THAN (128), PARTITION p2 VALUES LESS THAN MAXVALUE ); INSERT INTO t VALUES (NULL,0,24),(NULL,0,0),(0,21,0),(4,0,NULL),(1,8,2),(5,66,0); CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION; UPDATE v SET f2 = 1; # Cleanup DROP VIEW v; DROP TABLE t; {code}	{noformat:title=10.0 c3592ca7b886} 2017-10-29 20:13:21 7fa1aa52a700 InnoDB: Warning: using a partial-field key prefix in search. InnoDB: index `f2` of table `test`.`t` /* Partition `p1` /. Last data field length 6 bytes, InnoDB: key ptr now exceeds key end by 5 bytes. InnoDB: Key value in the MySQL format: len 6; hex 000000000204; asc ; 2017-10-29 20:13:21 7fa1aa52a700 InnoDB: Assertion failure in thread 140332324005632 in file row0sel.cc line 2498 InnoDB: Failing assertion: 0 {noformat} {noformat} #5 0x00007fa1a846c3fa in abort () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007fa1a1060e72 in row_sel_convert_mysql_key_to_innobase (tuple=0x7fa1945c43f0, buf=0x7fa1945c43ec "", buf_len=4, index=0x7fa1945ac278, key_ptr=0x7fa19479e40e '\245' <repeats 42 times>, "\377", key_len=6, trx=0x7fa194552278) at /data/src/10.0/storage/innobase/row/row0sel.cc:2498 #7 0x00007fa1a0f47856 in ha_innodb::index_read (this=0x7fa194481888, buf=0x7fa1944293a8 "\373", key_ptr=0x7fa19479e403 "", key_len=6, find_flag=HA_READ_KEY_EXACT) at /data/src/10.0/storage/innobase/handler/ha_innodb.cc:8114 #8 0x00007fa1a0f48ba3 in ha_innodb::rnd_pos (this=0x7fa194481888, buf=0x7fa1944293a8 "\373", pos=0x7fa19479e403 "") at /data/src/10.0/storage/innobase/handler/ha_innodb.cc:8687 #9 0x000000000083e828 in handler::ha_rnd_pos (this=0x7fa194481888, buf=0x7fa1944293a8 "\373", pos=0x7fa19479e403 "") at /data/src/10.0/sql/handler.cc:2648 #10 0x0000000000df1030 in ha_partition::rnd_pos (this=0x7fa194480888, buf=0x7fa1944293a8 "\373", pos=0x7fa19479e401 "\001") at /data/src/10.0/sql/ha_partition.cc:5063 #11 0x000000000083e7de in handler::ha_rnd_pos (this=0x7fa194480888, buf=0x7fa1944293a8 "\373", pos=0x7fa19479e401 "\001") at /data/src/10.0/sql/handler.cc:2648 #12 0x000000000071bd34 in multi_update::do_updates (this=0x7fa19475c308) at /data/src/10.0/sql/sql_update.cc:2365 #13 0x000000000071c35e in multi_update::send_eof (this=0x7fa19475c308) at /data/src/10.0/sql/sql_update.cc:2501 #14 0x00000000006ac107 in do_select (join=0x7fa19475c3c8, fields=0x7fa1aa528bd0, table=0x0, procedure=0x0) at /data/src/10.0/sql/sql_select.cc:17661 #15 0x0000000000688d11 in JOIN::exec_inner (this=0x7fa19475c3c8) at /data/src/10.0/sql/sql_select.cc:3093 #16 0x00000000006861ce in JOIN::exec (this=0x7fa19475c3c8) at /data/src/10.0/sql/sql_select.cc:2379 #17 0x0000000000689570 in mysql_select (thd=0x7fa19cb69070, rref_pointer_array=0x7fa19cb6d3a0, tables=0x7fa1945a4160, wild_num=0, fields=..., conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=1342177408, result=0x7fa19475c308, unit=0x7fa19cb6ca08, select_lex=0x7fa19cb6d0f8) at /data/src/10.0/sql/sql_select.cc:3318 #18 0x0000000000719679 in mysql_multi_update (thd=0x7fa19cb69070, table_list=0x7fa1945a4160, fields=0x7fa19cb6d210, values=0x7fa19cb6d6c8, conds=0x0, options=0, handle_duplicates=DUP_ERROR, ignore=false, unit=0x7fa19cb6ca08, select_lex=0x7fa19cb6d0f8, result=0x7fa1aa5292e0) at /data/src/10.0/sql/sql_update.cc:1597 #19 0x000000000064e4bd in mysql_execute_command (thd=0x7fa19cb69070) at /data/src/10.0/sql/sql_parse.cc:3377 #20 0x0000000000656c5e in mysql_parse (thd=0x7fa19cb69070, rawbuf=0x7fa1945a4088 "UPDATE v SET f2 = 1", length=19, parser_state=0x7fa1aa529640) at /data/src/10.0/sql/sql_parse.cc:6569 #21 0x000000000064979d in dispatch_command (command=COM_QUERY, thd=0x7fa19cb69070, packet=0x7fa1a25ef071 "UPDATE v SET f2 = 1", packet_length=19) at /data/src/10.0/sql/sql_parse.cc:1296 #22 0x0000000000648a9d in do_command (thd=0x7fa19cb69070) at /data/src/10.0/sql/sql_parse.cc:999 #23 0x0000000000768954 in do_handle_one_connection (thd_arg=0x7fa19cb69070) at /data/src/10.0/sql/sql_connect.cc:1377 #24 0x00000000007686c6 in handle_one_connection (arg=0x7fa19cb69070) at /data/src/10.0/sql/sql_connect.cc:1292 #25 0x0000000000ac91fe in pfs_spawn_thread (arg=0x7fa19cb19670) at /data/src/10.0/storage/perfschema/pfs.cc:1861 #26 0x00007fa1aa167494 in start_thread (arg=0x7fa1aa52a700) at pthread_create.c:333 #27 0x00007fa1a852093f in clone () from /lib/x86_64-linux-gnu/libc.so.6 {noformat} Also fails on 10.1 (38e12db478fde), 10.2 (e5678c3fac27af), 10.3 (ecee3c71e1e740). These are not first revisions where it started happening, in fact, it can be a rather old problem. _While fixing, please check all test cases below. They have subtle differences, but on some reason cause or don't cause crashes on different versions. Maybe it's just non-determinism, or maybe those differences are somehow important._ {code:sql\|title=Crash in 10.3} --source include/have_innodb.inc --source include/have_partition.inc CREATE TABLE t1 (a INT) ENGINE=InnoDB; CREATE TABLE t2 (b INT, c INT, KEY(b)) ENGINE=InnoDB PARTITION BY HASH(c) PARTITIONS 2; CREATE ALGORITHM = MERGE VIEW v AS SELECT a, b FROM t1 STRAIGHT_JOIN t2 WHERE b = 'foo' WITH CHECK OPTION; INSERT INTO t1 VALUES (1),(2); INSERT IGNORE INTO t2 VALUES (2,2),('three',3),(4,4); UPDATE v SET a = NULL ORDER BY a, b; DROP TABLE t1, t2; {code} {code:sql\|title=Crash in 10.0, 10.2 and 10.3} --source include/have_innodb.inc --source include/have_partition.inc SET GLOBAL innodb_stats_persistent= ON; CREATE TABLE t (f1 INT, f2 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY HASH (f1) PARTITIONS 2; INSERT IGNORE INTO t VALUES (NULL,0),(NULL,0),(0,21),(4,0),(1,8),(5,66); CREATE ALGORITHM=MERGE VIEW v AS SELECT t1. FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION; UPDATE v SET f2 = NULL; {code} {code:sql\|title=Crash in all 10.x} --source include/have_innodb.inc --source include/have_partition.inc CREATE TABLE t (f1 INT, f2 INT, f3 INT, KEY(f2)) ENGINE=InnoDB PARTITION BY RANGE (f1) ( PARTITION p0 VALUES LESS THAN (1), PARTITION p1 VALUES LESS THAN (128), PARTITION p2 VALUES LESS THAN MAXVALUE ); INSERT INTO t VALUES (NULL,0,24),(NULL,0,0),(0,21,0),(4,0,NULL),(1,8,2),(5,66,0); CREATE ALGORITHM=MERGE VIEW v AS SELECT t1.* FROM t t1 JOIN t t2 WHERE t1.f1 < t2.f2 WITH LOCAL CHECK OPTION; UPDATE v SET f2 = 1; # Cleanup DROP VIEW v; DROP TABLE t; {code}

Elena Stepanova made changes - 2017-10-29 18:16

Comment

[ Still happening:
https://internal.askmonty.org/buildbot/builders/win-rqg-se/builds/3200/steps/rqg_crash_tests/logs/stdio ]

Elena Stepanova made changes - 2017-10-29 18:17

Comment

[ Fresh occurrence on 10.1:
https://internal.askmonty.org/buildbot/builders/win-rqg-se/builds/3414/steps/rqg_crash_tests/logs/stdio ]

Elena Stepanova made changes - 2017-10-29 18:17

Comment

[ Recent occurrence in 10.2:
http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/40/steps/crash_summary/logs/stdio
{noformat}
2017-05-22 12:51:55 4040 [Warning] 'user' entry 'root@mariadb-04' ignored in --skip-name-resolve mode.
2017-05-22 12:51:55 4040 [Warning] 'proxies_priv' entry '@% root@mariadb-04' ignored in --skip-name-resolve mode.
Version: '10.2.6-MariaDB-debug-log' socket: '' port: 11500 Source distribution
2017-05-22 12:54:23 5240 [ERROR] mysqld.exe: Deadlock found when trying to get lock; try restarting transaction
2017-05-22 12:54:25 6964 [ERROR] mysqld.exe: Deadlock found when trying to get lock; try restarting transaction
2017-05-22 12:54:25 6964 [Warning] Sort aborted, host: 127.0.0.1, user: root, thread: 20, query: UPDATE view5 SET field4 = 43, field4 = 'm' ORDER BY field1, field2, field3, field4 /* QNO 7502 CON_ID 20 */
2017-05-22 12:56:21 5556 [Warning] InnoDB: Using a partial-field key prefix in search, index `rkr_index_5` of table `test`.`table_partitioned` /* Partition `p1`, Subpartition `p1sp0` */. Last data field length 5 bytes, key ptr now exceeds key end by 4 bytes. Key value in the MySQL format:
len 6; hex 000000000be7; asc ;
Assertion failed: 0, file D:\qa-win-debug\build\storage\innobase\row\row0sel.cc, line 2745
170522 12:56:21 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.6-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=65537
thread_count=12
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4195 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xeaadee0278
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:488]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!common_assert_to_stderr<wchar_t>()[assert.cpp:149]
mysqld.exe!_wassert()[assert.cpp:404]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2745]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9998]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:10605]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2611]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5033]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2611]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2398]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2540]
mysqld.exe!do_select()[sql_select.cc:18077]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3473]
mysqld.exe!JOIN::exec()[sql_select.cc:3275]
mysqld.exe!mysql_select()[sql_select.cc:3670]
mysqld.exe!mysql_multi_update()[sql_update.cc:1597]
mysqld.exe!mysql_execute_command()[sql_parse.cc:4315]
mysqld.exe!mysql_parse()[sql_parse.cc:7870]
mysqld.exe!dispatch_command()[sql_parse.cc:1814]
mysqld.exe!do_command()[sql_parse.cc:1361]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:346]
mysqld.exe!tp_callback()[threadpool_common.cc:192]
mysqld.exe!tp_callback()[threadpool_win.cc:378]
mysqld.exe!work_callback()[threadpool_win.cc:452]
ntdll.dll!RtlFreeUnicodeString()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xeaade94550): UPDATE view5 SET field2 = NULL, field1 = 114, field1 = 67 ORDER BY field1, field2, field3, field4 /* QNO 14804 CON_ID 19 */
Connection ID (thread ID): 19
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
Minidump written to E:\buildbot\vardirs\qa-win-debug\10.2-40\optim-crash-tests\current1_1\master-data\mysqld.dmp
DBI connect('host=127.0.0.1:port=11500:user=root:database=test','',...) failed: Can't connect to MySQL server on '127.0.0.1' (10061) at E:\buildbot\rqg\/lib/GenTest/Reporter/Deadlock.pm line 188 thread 49.
{noformat} ]

Elena Stepanova made changes - 2017-10-29 18:17

Comment

[ Fresh occurrence on 10.0:
http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/281/steps/crash_tests/logs/stdio
{noformat}
seed=1501795110
Command line:
E:\buildbot\rqg/runall.pl --no-mask --seed=time --threads=5 --duration=400 --queries=100M --reporters=QueryTimeout,Backtrace,ErrorLog,Deadlock,Shutdown --redefine=conf/mariadb/redefine_random_keys.yy --redefine=conf/mariadb/redefine_set_session_vars.yy --validators=TransformerNoComparator --transformers=ConvertSubqueriesToViews,DisableOptimizations,EnableOptimizations,ExecuteAsCTE,ExecuteAsInsertSelect,ExecuteAsPreparedOnce,ExecuteAsSelectItem,ExecuteAsUnion,ExecuteAsUpdateDelete,ExecuteAsView,NullIf,OrderBy,StraightJoin,ExecuteAsExecuteImmediate --grammar=conf/optimizer/updateable_views.yy --mysqld=--default-storage-engine=InnoDB --mysqld=--init-file=E:/buildbot/rqg/conf/optimizer/updateable_views.init --mtr-build-thread=150 --basedir1=D:\qa-win-debug\build --vardir1=E:\buildbot\vardirs\qa-win-debug\10.0-281\optim-crash-tests/current1_1
{noformat} ]

Elena Stepanova made changes - 2017-10-29 18:17

Comment

[ Closing as a duplicate of ~~MDEV-13838~~, because the other one has a ready-to-use test case. ]

Elena Stepanova made changes - 2017-10-29 18:17

Comment

[ ~~MDEV-13838~~ is already fixed in 10.2, but the failure is still happening:
http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/687/steps/crash_tests/logs/stdio

{noformat}
Assertion failed: 0, file D:\qa-win-debug\build\storage\innobase\row\row0sel.cc, line 2724
171025 13:15:58 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.10-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=65537
thread_count=12
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4211 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x261da2e798
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:488]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!common_assert_to_stderr<wchar_t>()[assert.cpp:149]
mysqld.exe!_wassert()[assert.cpp:404]
mysqld.exe!row_sel_convert_mysql_key_to_innobase()[row0sel.cc:2724]
mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9785]
mysqld.exe!ha_innobase::rnd_pos()[ha_innodb.cc:10392]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2603]
mysqld.exe!ha_partition::rnd_pos()[ha_partition.cc:5071]
mysqld.exe!handler::ha_rnd_pos()[handler.cc:2603]
mysqld.exe!multi_update::do_updates()[sql_update.cc:2418]
mysqld.exe!multi_update::send_eof()[sql_update.cc:2560]
mysqld.exe!do_select()[sql_select.cc:18174]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3483]
mysqld.exe!JOIN::exec()[sql_select.cc:3279]
mysqld.exe!mysql_select()[sql_select.cc:3680]
mysqld.exe!mysql_multi_update()[sql_update.cc:1597]
mysqld.exe!mysql_execute_command()[sql_parse.cc:4319]
mysqld.exe!mysql_parse()[sql_parse.cc:7861]
mysqld.exe!dispatch_command()[sql_parse.cc:1807]
mysqld.exe!do_command()[sql_parse.cc:1359]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:366]
mysqld.exe!tp_callback()[threadpool_common.cc:192]
mysqld.exe!tp_callback()[threadpool_win.cc:378]
mysqld.exe!work_callback()[threadpool_win.cc:452]
ntdll.dll!RtlFreeUnicodeString()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x261d9a2c50): UPDATE view3 SET field1 = 'to', field1 = 145 ORDER BY field1, field2, field3, field4 /* QNO 5277 CON_ID 21 */
Connection ID (thread ID): 21
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
{noformat} ]

Elena Stepanova made changes - 2017-10-29 18:17

Assignee

Elena Stepanova [ elenst ]

Marko Mäkelä [ marko ]

Marko Mäkelä made changes - 2017-10-31 17:19

Summary

InnoDB: Failing assertion: 0 in file row0sel.cc line 2498

InnoDB: Warning: using a partial-field key prefix in search

Marko Mäkelä made changes - 2017-10-31 17:27

Link

This issue duplicates ~~MDEV-13838~~ [ ~~MDEV-13838~~ ]

Sergei Golubchik made changes - 2017-10-31 17:55

Assignee

Marko Mäkelä [ marko ]

Elena Stepanova made changes - 2017-11-17 00:06

Link

This issue is duplicated by ~~MDEV-14408~~ [ ~~MDEV-14408~~ ]

Elena Stepanova made changes - 2017-11-17 11:20

Summary

InnoDB: Warning: using a partial-field key prefix in search

InnoDB: Warning: using a partial-field key prefix in search, results in assertion failure or "Can't find record" error

Alice Sherepa made changes - 2018-05-22 09:30

Link

This issue relates to ~~MDEV-16240~~ [ ~~MDEV-16240~~ ]

Sergei Golubchik made changes - 2018-06-11 09:12

Assignee

Marko Mäkelä [ marko ]

Marko Mäkelä made changes - 2018-06-21 14:58

Assignee

Marko Mäkelä [ marko ]

Oleksandr Byelkin [ sanja ]

Oleksandr Byelkin made changes - 2018-07-11 10:43

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Oleksandr Byelkin made changes - 2018-07-16 13:38

Assignee

Oleksandr Byelkin [ sanja ]

Marko Mäkelä [ marko ]

Marko Mäkelä made changes - 2018-08-29 13:39

Assignee

Marko Mäkelä [ marko ]

Oleksandr Byelkin [ sanja ]

Oleksandr Byelkin made changes - 2018-08-30 13:31

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Oleksandr Byelkin made changes - 2018-08-30 13:31

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Julien Fritsch made changes - 2018-10-12 16:08

Priority

Major [ 3 ]

Critical [ 2 ]

Oleksandr Byelkin made changes - 2018-11-02 17:09

Assignee	Oleksandr Byelkin [ sanja ]	Sergei Golubchik [ serg ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Sergei Golubchik made changes - 2018-11-02 17:19

Assignee	Sergei Golubchik [ serg ]	Oleksandr Byelkin [ sanja ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Oleksandr Byelkin made changes - 2018-11-07 08:40

issue.field.resolutiondate

2018-11-07 08:40:23.0

2018-11-07 08:40:23.673

Oleksandr Byelkin made changes - 2018-11-07 08:40

Fix Version/s		10.1.38 [ 23209 ]
Fix Version/s		10.0.38 [ 23211 ]
Fix Version/s		10.2.20 [ 23212 ]
Fix Version/s	10.2 [ 14601 ]
Fix Version/s	10.0 [ 16000 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:43

Workflow

MariaDB v3 [ 78122 ]

MariaDB v4 [ 151141 ]

Jira Automation (IT) made changes - 2024-07-04 08:46

Zendesk Related Tickets

102587

MariaDB Server

InnoDB: Warning: using a partial-field key prefix in search, results in assertion failure or "Can't find record" error

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration