I even understand that 5.0 is running out of active support (I’m not questioning that you’ll stop supporting 4.1 entirely too), and you’ll stop doing pretty much anything to 5.0, except “critical security fixes” (w00t, I managed to get one into 4.1, 8 year old MITM flaw :).
I really understand that supporting more than one release is very very very difficult, and people should do only adjacent version upgrade.
I’m not asking you much, but, maybe you could then support 5.1 to 5.1 replication? I don’t want much, just:
- Gracefully recover after slave crashes.
- Don’t have single serial reading of pages for replication stream as a bottleneck – either read-ahead properly (you can do that with RBR!!!), or apply events in parallel (you can do that with RBR too!)
- Allow to edit replication filters without restarting servers.
- Allow to enable and disable binary logging of events received from master, as well as enabling and disabling binary logging without restarting the instance.
I hope it isn’t too much too ask! It is just supported replication between two same version instances.