Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21047

Crash on UTF-8 Full text search

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 10.4.10
    • 10.4.11
    • Optimizer
    • Centos os 7

    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;

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21040 InnoDB: fulltext search with ` in(...)` crashed on specific combination

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20407 mysqld got signal 11; rowid filter

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21125 Crash with FTS query

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

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

            marko Marko Mäkelä added a comment - I would appreciate a full SQL test case. This could be similar to MDEV-21040 .
            marko Marko Mäkelä added a comment -

            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.

            marko Marko Mäkelä added a comment - 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 .
            uisoftware Mohammad Tanhaei added a comment -

            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.

            uisoftware Mohammad Tanhaei added a comment - 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.
            marko Marko Mäkelä added a comment -

            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.

            marko Marko Mäkelä added a comment - 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.
            elenst Elena Stepanova added a comment -

            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.

            elenst Elena Stepanova added a comment - 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.
            igor Igor Babaev added a comment -

            Most probably this this a duplicate of MDEV-20407.

            igor Igor Babaev added a comment - Most probably this this a duplicate of MDEV-20407 .

            People

              igor Igor Babaev
              uisoftware Mohammad Tanhaei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.