Merged
Conversation
…ed by frontend and backend.
Contributor
|
retest this please |
1 similar comment
Contributor
|
retest this please |
14123ff to
9900691
Compare
…specific source file and line number.
To enable coredump feature, specify the filename and line number in the coredump_filters table.
Example:
INSERT INTO coredump_filters (filename,line) VALUES ('mysql_data_stream.cpp', 498);
LOAD COREDUMP TO RUNTIME;
Note:
* It is important to note that coredump filters cannot be persisted on disk and will always be empty when a new instance is created.
* Filenames are case-sensitive
* 'admin-coredump_generation_threshold', has been introduced to specify the maximum number of core files that can be generated.
* 'admin-coredump_generation_interval_ms', has been implemented to define the time gap between the generation of core files.
9900691 to
c4dae72
Compare
renecannao
added a commit
that referenced
this pull request
Dec 19, 2025
Add comprehensive documentation for the on‑demand core dump generation feature introduced in PR #4225. The documentation covers: - coredump_filters and runtime_coredump_filters table definitions - LOAD COREDUMP TO RUNTIME admin command and its aliases - Configuration variables admin‑coredump_generation_threshold and admin‑coredump_generation_interval_ms - Usage examples with INSERT and LOAD commands - Important notes about case‑sensitive filenames, runtime‑only behavior, rate limiting, and platform support - Troubleshooting guidance and best practices The documentation addresses the missing documentation reported in GitHub issue #5213.
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
3 participants
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.
Feature for troubleshooting purposes. It allows capturing and storing data packet history for easier debugging and analysis.
The history queue will aid in troubleshooting frontend and backend communication issues by providing a record of the packets exchanged.
By default this feature is disabled. To activate this feature, you need to configure the 'mysql-data_packets_history_size' variable to the desired maximum size for storing data packets. When the number of incoming or outgoing packets exceeds this limit, oldest packets are removed from the queue to make room for the new ones.
Implemented the functionality to generate a coredump upon reaching a specific source file and line number.
To enable coredump feature, specify the filename and line number in the coredump_filters table.
Example:
Note:
Coredump filters cannot be persisted on disk and will always be empty when a new instance is created.
Filenames are case-sensitive
'admin-coredump_generation_threshold', has been introduced to specify the maximum number of core files that can be generated.
'admin-coredump_generation_interval_ms', has been implemented to define the time gap between the generation of core files.