Everybody affected by this bug -
Can you still reproduce it, or have there been any past incidents, with --relay_log_recovery set to ON? The requirement for this setting has not been documented in our crash-resistant slave docs.
Everybody affected by this bug -
Can you still reproduce it, or have there been any past incidents, with --relay_ log_recovery set to ON? The requirement for this setting has not been documented in our crash-resistant slave docs.