MDEV-38832 Assertion `!commit_lsn' failed in void trx_t::free()#4650
Open
Thirunarayanan wants to merge 1 commit into11.8from
Open
MDEV-38832 Assertion `!commit_lsn' failed in void trx_t::free()#4650Thirunarayanan wants to merge 1 commit into11.8from
Thirunarayanan wants to merge 1 commit into11.8from
Conversation
|
|
Problem: ======== When creating tables with vector indexes, if the secondary table creation fails after the main table is successfully created, the server was not properly cleaning up the main table's .ibd file. When we try to do DROP DATABASE, the server sees an orphaned file and attempts to clean up a "stale" handle. If innodb_flush_log_later trx_commit=0 is set then the log buffer is written to the file and flushed to disk only once per second. Due to this reason, InnoDB doesn't reset trx->commit_lsn to 0. This lead to assertion failure in trx_t::free() Reason: ======= This occurred because create_table_impl() always called ddl_log_complete() on any error, which disables DDL log entries instead of executing them for cleanup. The main table would be left behind even though the overall CREATE TABLE operation failed. Solution: ========= ha_create_table(): Return error code 2 specifically when secondary table creation for high-level indexes fails create_table_impl(): Call ddl_log_revert() when error code is 2 to properly clean up the main table files. innodb_drop_database(): Add debug assertion reset to clear commit_lsn before freeing the transaction.
ecaca26 to
588e95b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem:
When creating tables with vector indexes, if the secondary table creation fails after the main table is successfully created, the server was not properly cleaning up the main table's .ibd file. When we try to do DROP DATABASE, the server sees an orphaned file and attempts to clean up a "stale" handle. If
innodb_flush_log_later trx_commit=0 is set then the log buffer is written to the file and flushed to disk only once per second. Due to this reason, InnoDB doesn't reset trx->commit_lsn to 0. This lead to assertion failure in trx_t::free()
Reason:
This occurred because create_table_impl() always called ddl_log_complete() on any error, which disables DDL log entries instead of executing them for cleanup. The main table would be left behind even though the overall CREATE TABLE operation failed.
Solution:
ha_create_table(): Return error code 2 specifically when secondary table creation for high-level indexes fails
create_table_impl(): Call ddl_log_revert() when error code is 2 to properly clean up the main table files.
innodb_drop_database(): Add debug assertion reset to clear commit_lsn before freeing the transaction.