[MDEV-21047] Crash on UTF-8 Full text search Created: 2019-11-14  Updated: 2020-12-08  Resolved: 2019-11-27

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.4.10
Fix Version/s: 10.4.11

Type: Bug Priority: Blocker
Reporter: Mohammad Tanhaei Assignee: Igor Babaev
Resolution: Fixed Votes: 0
Labels: crash
Environment:

Centos os 7

Attachments: File mysql.err    
Issue Links:
Relates
relates to MDEV-21040 InnoDB: fulltext search with ` in(...... Closed
relates to MDEV-20407 mysqld got signal 11; rowid filter Closed
relates to MDEV-21125 Crash with FTS query Closed

 Description   

You can reproduce the problem by creating an table that have a Full-text index and then search with charset other than latin1.
For reproducing the bug you should use several other indexes along the full-text search.

For example:

SELECT t.* FROM threads t WHERE [some other search based on indexes] MATCH (t.subject) AGAINST ('Some Arabic/Persian Text') >= '3' ORDER BY t.tid DESC LIMIT 0, 10;

 Comments   
Comment by Marko Mäkelä [ 2019-11-14 ]

I would appreciate a full SQL test case. This could be similar to MDEV-21040.

Comment by Marko Mäkelä [ 2019-11-15 ]

uisoftware, can you please try to resolve these symbols from mysql.err?

/usr/sbin/mysqld(+0xb3335c)[0x55c42d34e35c]
 
/usr/sbin/mysqld(+0x5a05d9)[0x55c42cdbb5d9]
 
/usr/sbin/mysqld(+0x5a0885)[0x55c42cdbb885]
 
/usr/sbin/mysqld(+0xb361dd)[0x55c42d3511dd]
 
/usr/sbin/mysqld(+0xa5404d)[0x55c42d26f04d]
 
/usr/sbin/mysqld(_ZN9FT_SELECT8get_nextEv+0x1d)[0x55c42d1ef92d]
 
/usr/sbin/mysqld(_Z8filesortP3THDP5TABLEP8FilesortP16Filesort_trackerP4JOINy+0x954)[0x55c42d0c0ff4]
 
/usr/sbin/mysqld(_Z17create_sort_indexP3THDP4JOINP13st_join_tableP8Filesort+0xd7)[0x55c42cefd597]
 
/usr/sbin/mysqld(_ZN13st_join_table10sort_tableEv+0x73)[0x55c42cefd8b3]

To do that, please ensure that you have the debugging symbols installed and then do:

gdb /usr/sbin/mysqld
 
list *0xb3335c
 
list *0x5a05d9
 
list *0x5a0885
 
list *0xb361dd
 
list *0xa5404d
 
quit

That would help us determine whether this bug is a duplicate of MDEV-21040.

Comment by Mohammad Tanhaei [ 2019-11-15 ]

Removing an index that contains three columns in the problematic table resolved my problem. It seems that Full-Text index has some conflicts with other indexes that have several columns. The problem only occurs on none latin character selections (UTF-8 chars).
Thanks in advance.

Comment by Marko Mäkelä [ 2019-11-15 ]

uisoftware, unfortunately it is not clear in which part of the code the crash occurred. We would need either a complete set of SQL statements for reproducing the problem, or at the very least, a resolved stack trace of the crash.

As far as I understand, the internal structure of the inverted index for the InnoDB fulltext index is independent on the number of columns that are part of the index. However, if this indeed is the same issue as in MDEV-21040 (which was verified to be a regression caused by MDEV-16188), the number of columns might affect the incorrect operation of the SQL layer above InnoDB.

Comment by Elena Stepanova [ 2019-11-18 ]

uisoftware, if you know the way to reproduce the failure, please provide the actual server options, CREATE TABLE statement and further queries which lead to the problem rather than a verbal description of them.

Comment by Igor Babaev [ 2019-11-27 ]

Most probably this this a duplicate of MDEV-20407.

Generated at Thu Feb 08 09:04:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.