Following behaviour is not consistent with normal MySQL replication (ROW based):
1 - "ONE TIME" events are not dropped on slave nodes after expiring on master (event creator node)
2 - After doing ALTER EVENT, slave nodes end up with empty Definer "@"
Following Issues with SST probably need documenting and/or warnings in error log:
- After SST from master node (the one where event is ENABLED) - you will end up with the event enabled on two nodes, hence it's now being executed twice
- If event owner node is re-created using SST, all the nodes have the event now in "SLAVESIDE_DISABLED" state, hence manual action is needed to re-enable the event on one of the nodes.
Especially having an event ENABLED on more then one node may be problematic and maybe automatically checked and disabled on joiner.
Following behaviour is not consistent with normal MySQL replication (ROW based):
1 - "ONE TIME" events are not dropped on slave nodes after expiring on master (event creator node)
2 - After doing ALTER EVENT, slave nodes end up with empty Definer "@"
Following Issues with SST probably need documenting and/or warnings in error log: DISABLED" state, hence manual action is needed to re-enable the event on one of the nodes.
- After SST from master node (the one where event is ENABLED) - you will end up with the event enabled on two nodes, hence it's now being executed twice
- If event owner node is re-created using SST, all the nodes have the event now in "SLAVESIDE_
Especially having an event ENABLED on more then one node may be problematic and maybe automatically checked and disabled on joiner.