Set correct backend encryption when switching to fast_forward #4114
Conversation
This file contains 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
Patching mariadb_rpl.c and mariadb_rpl.h to recognize (recognize only, no processing) GTID events and V2 events.
When receiving MYSQL_COM_BINLOG_DUMP , MYSQL_COM_BINLOG_DUMP_GTID or MYSQL_COM_REGISTER_SLAVE , proxysql automatically switches to fast_forward . Although it is important to correctly configure "encrypted" in the backend data stream if needed. Used PMC-10005 for reference , as this is implemented similarly in many parts of the code. During the switch proxy_info() now also reports the client and the command received.
|
retest this please |
1 similar comment
|
retest this please |
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.
Set correct backend encryption when switching to fast_forward because of
MYSQL_COM_BINLOG_DUMP,MYSQL_COM_BINLOG_DUMP_GTIDorMYSQL_COM_REGISTER_SLAVE