Disable binlogging when running with --test-on-replica?
Open
question
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
What would you think about running `SET SESSION sql_log_bin=0` before applying changes when running in `--test-on-replica` mode? Right now, after testing on a replica, we need to wipe it and restore it from scratch (to prevent any invalid GTIDs from creeping in the event of a later promotion of that host to master). This is kind of irritating, and if we just turn off binlogging for that session, we wouldn't necessarily have to reset the box afterwards.
Contributor guide
Assessment
This issue has not been assessed yet.