So, let's see what JD says.
Here he goes:
When you want to use replication, you ought to run these commands
Not sure which commands you're talking about. In the specific case of stop_replication, it's a kill switch in the proper sense (quote from wikipedia):
a kill switch is designed and configured to a) completely abort the operation at all costs and b) be operable in a manner that is quick, simple (so that even a panicking user with impaired executive function can operate it), and, usually, c) be obvious even to an untrained operator or a bystander
We hit on a) and b), the c) part might not be there yet. The issue here is that the command is respected on the master cluster (when ran there) but not on the slave cluster (when ran there).
If you stop replication on the master, the logs are no longer stored to be pushed down stream like they would with replication enabled.
The bug, however, causes the slave to keep accepting logs even while disabled although the other processes on slave cluster respect the disabled flag
Since it's a kill switch, what's going to happen is the slave cluster is going to drop the log edits. This is not what you want, you want is
So, afaik, running commands on the slave cluster are futile as its the master cluster which does all the work.
I think you understand the issue here reasonably well, and indeed most of the commands won't do anything on the slave cluster, except here the kill switch should stop all replication-related activity including applying incoming logs.