Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
10.2.14
-
Linux version 3.10.0-862.3.3.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Fri Jun 15 04:15:27 UTC 2018
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 653
Server version: 10.2.14-MariaDB-10.2.14+maria~jessie mariadb.org binary distribution
Linux version 3.10.0-862.3.3.el7.x86_64 ( builder@kbuilder.dev.centos.org ) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC) ) #1 SMP Fri Jun 15 04:15:27 UTC 2018 Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 653 Server version: 10.2.14-MariaDB-10.2.14+maria~jessie mariadb.org binary distribution
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
Issue Links
- includes
-
-
- Closed
-
- is part of
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is part of |
Is it reproducible by re-running the same query? I assume it must be, if you are saying it's a critical production issue.
Please provide the output of
SHOW CREATE TABLE product_matching_candidates; |
SHOW INDEX IN product_matching_candidates; |
SHOW GLOBAL VARIABLES; |
| Epic/Theme | service |
| Labels | connect-engine crash innodb optimizer | need_feedback |
| Component/s | Server [ 13907 ] | |
| Component/s | Configuration [ 13904 ] |
| Attachment | Tableinfo&Indexinfo.txt [ 46509 ] |
| Attachment | globalvariables.txt [ 46510 ] |
[^Tableinfo&Indexinfo.txt globalvariables.txt
]
Including Attachments and waiting for reply.
| Labels | need_feedback |
Are you waiting for anything from my end ?
Actually yes, an answer to the question "Is it reproducible by re-running the same query?"
| Labels | need_feedback |
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?
| Fix Version/s | N/A [ 14700 ] | |
| Resolution | Incomplete [ 4 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
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.
| Link |
This issue includes |
| Workflow | MariaDB v3 [ 89639 ] | MariaDB v4 [ 154947 ] |
Any Update on the issue ?? This is critical production issue