Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
-
1.2.3
-
None
Description
Customer report issue. They found a related bug fix in mariadb server, but it looks to be specific with InnoDB tables. They had the problem on a Columnstore Table.
From customer:
The query that pewrformed an update of a column store table record in the production database got stuck on "Init for update" state. At least I saw it being in that state for 4334 before I killed that process.
I think it is caused by some type of misconfiguration because the very same query on the vary same table (with the very same content) went through just fine in our development instance. I set it up for verification purposes to be exactly the same. The only different thing was the database instance. I tried to compare configuration files but did not spot any difference.
Please point me somewhere I can learn about how to deal with this issue. I found this JIRA ticket online: https://jira.mariadb.org/browse/MDEV-15214 but not sure if the fix for this is a part of ColumnStore distro.