[MDEV-6082] Assertion `0' fails in TC_LOG_DUMMY::log_and_order on DML after installing TokuDB at runtime on server with disabled InnoDB Created: 2014-04-12 Updated: 2019-05-30 Resolved: 2014-07-28 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.36, 10.0.10 |
| Fix Version/s: | 5.5.39, 10.0.13 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
I set it to minor, because the pre-conditions don't seem to be common: disabled InnoDB plus installing TokuDB at runtime. MTR test case:
The same SQL causes the failure without MTR, too, but make sure that the server is started with
and it does not have TokuDB installed yet.
Stack trace from:
|
| Comments |
| Comment by Rich Prohaska [ 2014-04-29 ] |
|
TC_LOG_DUMMY is used if the number of XA storage engines is <= 1 when mysqld initializes. If an XA storage engine is installed later one, there is no code to redo the initialization of the logs. One currently must restart mysqld instead. |
| Comment by Sergei Golubchik [ 2014-07-27 ] |
|
As a fix I'll disable XA in the loaded engine (with a warning). Trying to switch tc_log implementation run-time may be too risky for this uncommon scenario. |