I think the issue is that there is too much configuration replicated to all nodes, and since this can be changed and replicated from nodes then one node can change configuration of all or part of the replication system.
I have several groups, but every node has configuration from other groups, not only its group. Some tables with this issue are, node_group, parameter, trigger, routers, etc..
Is any why to enforce nodes to have only its relevant configuration?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is working as designed, all configuration is sent to all nodes. Each node will only apply the configuration that it needs. We use the same change capture techniques to replication configuration so that it is in sync at all nodes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the issue is that there is too much configuration replicated to all nodes, and since this can be changed and replicated from nodes then one node can change configuration of all or part of the replication system.
I have several groups, but every node has configuration from other groups, not only its group. Some tables with this issue are, node_group, parameter, trigger, routers, etc..
Is any why to enforce nodes to have only its relevant configuration?
Thanks
This is working as designed, all configuration is sent to all nodes. Each node will only apply the configuration that it needs. We use the same change capture techniques to replication configuration so that it is in sync at all nodes.