Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.2.14
    • N/A
    • Server

    Description

      DB got restarted in Production environment.

      Table is marked as crashed and should be repaired. All crashed tables are ISAM tables, INNODB tables are fine and not crashing in the database. Insert and Updates are run on this crashing tables

      Attachments

        1. Error.log
          9 kB
        2. globalvariables.txt
          445 kB
        3. Tableinfo&Indexinfo.txt
          4 kB

        Issue Links

          Activity

            elenst Elena Stepanova added a comment - - edited

            Are you waiting for anything from my end ?

            Actually yes, an answer to the question "Is it reproducible by re-running the same query?"

            elenst Elena Stepanova added a comment - - edited Are you waiting for anything from my end ? Actually yes, an answer to the question "Is it reproducible by re-running the same query?"
            s.tausiff@animalytix.com Syed Tausiff added a comment -

            We are not able to reproduce the crash every time we ran the query and Table is crashing due to Select,alter,update and insert queries.
            We do not have a continuous crash.
            We narrowed down the issue and found its because of stored generated field in the table.

            Can you confirm us if there is any bug in stored generated column's ?

            s.tausiff@animalytix.com Syed Tausiff added a comment - We are not able to reproduce the crash every time we ran the query and Table is crashing due to Select,alter,update and insert queries. We do not have a continuous crash. We narrowed down the issue and found its because of stored generated field in the table. Can you confirm us if there is any bug in stored generated column's ?

            We have some known bugs related to virtual generated columns, although i can't find anything obviously related about stored columns. We might still have something, but due to a missing stack trace in the error log we cannot match this crash with any particular known bug. Would you be able to acquire a coredump and run gdb --batch --eval-command="thread apply all bt" <path to mysqld binary> <path to coredump> on it?

            elenst Elena Stepanova added a comment - We have some known bugs related to virtual generated columns, although i can't find anything obviously related about stored columns. We might still have something, but due to a missing stack trace in the error log we cannot match this crash with any particular known bug. Would you be able to acquire a coredump and run gdb --batch --eval-command="thread apply all bt" <path to mysqld binary> <path to coredump> on it?
            s.tausiff@animalytix.com Syed Tausiff added a comment -

            Hi,

            Can you provide any other solution or is it mandatory to run acquire a coredump and run gdb --batch --eval-command="thread apply all bt" <path to mysqld binary> <path to coredump> ?

            We are still having this issue. To make a note this database is in docker and there are stored generated columns in the tables, either one of the above things is causing crash ?

            s.tausiff@animalytix.com Syed Tausiff added a comment - Hi, Can you provide any other solution or is it mandatory to run acquire a coredump and run gdb --batch --eval-command="thread apply all bt" <path to mysqld binary> <path to coredump> ? We are still having this issue. To make a note this database is in docker and there are stored generated columns in the tables, either one of the above things is causing crash ?

            An alternative solution would be to acquire a support contract, as it's customary for critical production environments. In this case support engineers could assist you at investigating the problem. If you already have a support contract, please submit a support ticket.

            elenst Elena Stepanova added a comment - An alternative solution would be to acquire a support contract, as it's customary for critical production environments. In this case support engineers could assist you at investigating the problem. If you already have a support contract, please submit a support ticket.

            People

              Unassigned Unassigned
              s.tausiff@animalytix.com Syed Tausiff
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.