-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle_fatal_signal (sig=11) in thd_ha_data #129
Comments
The problem looks to be the innodb plugin is disabled, but the innodb_* plugins for information schema are all still running, so requests through information schema for innodb status can cause the system to crash. Could you disable the buffer_page plugin on startup with --skip-innodb-buffer-page for your tests? The other plugins look to function without crashing in the absence of innodb. |
@hermanlee sure can do! Thank you! Will update if I still see similar crashes after using --skip-innodb-buffer-page. Thanks |
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. #129 Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled. Reviewers: hermanlee4, yoshinorim Reviewed By: yoshinorim Subscribers: webscalesql-eng Differential Revision: https://reviews.facebook.net/D52959
@hermanlee @jkedgar Thanks. Does this mean I should be able to remove --skip-innodb-buffer-page from default test setup? Thank you |
Yes. It will now get a warning that the table is not available when InnoDB is not present, but it will no longer crash without that flag. |
Thank you @jkedgar |
--skip-innodb-buffer-page was removed from all tests |
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook/mysql-5.6#129 Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled. Reviewers: hermanlee4, yoshinorim Reviewed By: yoshinorim Subscribers: webscalesql-eng Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook/mysql-5.6#129 Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled. Reviewers: hermanlee4, yoshinorim Reviewed By: yoshinorim Subscribers: webscalesql-eng Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. #129 Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled. Reviewers: hermanlee4, yoshinorim Reviewed By: yoshinorim Subscribers: webscalesql-eng Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Test Plan: MTR with new test that attempts to SELECT from all INNODB INFORMATION_SCHEMA tables with InnoDB disabled. Reviewers: hermanlee4, yoshinorim Reviewed By: yoshinorim Subscribers: webscalesql-eng Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. #129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3ac0a37
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959 fbshipit-source-id: 3787173e8ff
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook/mysql-5.6#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook#129 Differential Revision: https://reviews.facebook.net/D52959
Summary: Currently disabling InnoDB does not automatically disable all the INFORMATION_SCHEMA tables that are associated with InnoDB and attempting to access one of them causes a segfault. Make sure all InnoDB INFORMATION_SCHEMA tables are disabled when InnoDB is disabled. facebook/mysql-5.6#129 Differential Revision: https://reviews.facebook.net/D52959
This bug is partly blocking QA efforts as it is seen in many trials. Thank you.
The text was updated successfully, but these errors were encountered: