Details

    Description

      We have a customer continuously getting this in their error log:

      InnoDB: Error (Duplicate key) writing word node to FTS auxiliary index table.
      

      I haven't been able to reproduce this issue on my side. But looking through the source code, it doesn't seem like this type of error should be reported in the error log. Perhaps it could be better handled internally (silently ignored?).

      This is a problem because it uselessly fills up the error log.

      Thanks,
      -will

      2017-08-10 - A careful code review would be needed to answer the question if this has any user-visible impact, or why this occurs in the first place.

      Attachments

        Issue Links

          Activity

            wfong Will Fong created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            Affects Version/s 10.0.29 [ 22312 ]
            elenst Elena Stepanova made changes -
            Component/s Full-text Search [ 10104 ]
            Fix Version/s 10.0 [ 16000 ]
            Assignee Marko Mäkelä [ marko ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            julien.fritsch Julien Fritsch made changes -
            Description We have a customer continuously getting this in their error log:

            {noformat}
            InnoDB: Error (Duplicate key) writing word node to FTS auxiliary index table.
            {noformat}

            I haven't been able to reproduce this issue on my side. But looking through the source code, it doesn't seem like this type of error should be reported in the error log. Perhaps it could be better handled internally (silently ignored?).

            This is a problem because it uselessly fills up the error log.

            Thanks,
            -will
            We have a customer continuously getting this in their error log:

            {noformat}
            InnoDB: Error (Duplicate key) writing word node to FTS auxiliary index table.
            {noformat}

            I haven't been able to reproduce this issue on my side. But looking through the source code, it doesn't seem like this type of error should be reported in the error log. Perhaps it could be better handled internally (silently ignored?).

            This is a problem because it uselessly fills up the error log.

            Thanks,
            -will

            2017-08-10 - A careful code review would be needed to answer the question if this has any user-visible impact, or why this occurs in the first place.
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            marko Marko Mäkelä made changes -
            Labels upstream
            marko Marko Mäkelä made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            Component/s Storage Engine - XtraDB [ 10135 ]
            Fix Version/s 10.0.33 [ 22552 ]
            Fix Version/s 10.1.29 [ 22636 ]
            Fix Version/s 10.2.10 [ 22615 ]
            Fix Version/s 10.3.3 [ 22644 ]
            Fix Version/s 10.0 [ 16000 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 80589 ] MariaDB v4 [ 152079 ]
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 185450

            People

              marko Marko Mäkelä
              wfong Will Fong
              Votes:
              2 Vote for this issue
              Watchers:
              10 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.