Semantics of RSU claims that action executed are local to the node and so local UUID is incremented and not the shared clustered UUID. Setting wsrep_on=0 will have same effect of incrementing local UUID.
Ideally, for multi-master solution user shouldn't execute local actions but blocking it would be harsh since there are valid use-cases when user need to run something locally.
As per the protocol of GTID (from MySQL) each action (local/remote) should have a GTID associated with it. sql_log_bin comes as rescue as MySQL semantics dictates use use of sql_log_bin controlling write to binary logs.
With those clarification I don't foresee why RSU should change binary logging behavior.
Let's understand the semantics.
Semantics of RSU claims that action executed are local to the node and so local UUID is incremented and not the shared clustered UUID. Setting wsrep_on=0 will have same effect of incrementing local UUID.
Ideally, for multi-master solution user shouldn't execute local actions but blocking it would be harsh since there are valid use-cases when user need to run something locally.
As per the protocol of GTID (from MySQL) each action (local/remote) should have a GTID associated with it. sql_log_bin comes as rescue as MySQL semantics dictates use use of sql_log_bin controlling write to binary logs.
With those clarification I don't foresee why RSU should change binary logging behavior.