fix - Bug/increase history list length #431
Merged
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.
Overview
issue number #430
When using the
pymysqlreplication
package, there was a recurring issue with thehistory list length
value under the following circumstances:This problem led to a gradual slowing down of SELECT queries.
For detailed information, you can refer to the following reference:
https://minervadb.xyz/troubleshooting-innodb-history-length-with-hung-mysql-transaction/
As a result, I investigated the problem area and made necessary modifications. After making the changes, you were able to compare the performance before and after the fix, using monitoring tools such as Prometheus and MySQL Exporter.
Fixed
Modified code
Performance Comparison After the Code Modifications
Before modification

After modification
