Bug #6178 | unwanted relay-bin.xxx files after 'FLUSH LOGS' command | ||
---|---|---|---|
Submitted: | 20 Oct 2004 13:27 | Modified: | 21 Oct 2004 22:35 |
Reporter: | johan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 4.0.18 | OS: | Microsoft Windows (Windows2000) |
Assigned to: | Lars Thalmann | CPU Architecture: | Any |
[20 Oct 2004 13:27]
johan
[21 Oct 2004 22:13]
Lars Thalmann
Hi Johan, For having the FLUSH LOGS command not flushing the relay log, you must execute RESET SLAVE. But, please look at option --bin-log-size for controlling the size of your binlog. Setting this option to a good value would make it unnecessary to execute FLUSH LOGS as often as you do now. Hopefully that will make things easier for you.
[21 Oct 2004 22:35]
Guilhem Bichot
Sorry, Lars meant max_binlog_size; which does: "Binary log will be rotated automatically when the size exceeds this \ value. Will also apply to relay logs if max_relay_log_size is 0. \ The minimum value for this variable is 4096." (so better set max_relay_log_size to something else than 0).