-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
Normal
It's not allowed to create producers with their subtrees conflict.
Further comments from rovarga:
I think we need to revise the entire idea of producer exclusivity. It makes interaction between RESTCONF and applications problematic (i.e. if an app writes to the config datastore, restconf won't ever be able to interfere) and there actually are users who use the overlap – making the migration a huge pain.
On clustering side of things, exclusivity does not quite work with partitions and the fact that producer allocation is synchronous: in cluster we need to ensure cluster-wide sync on what producers are there and need to eject disconnected nodes.
- relates to
-
CONTROLLER-1740 Producer un-registration on isolated node is never propagated to the rest of the cluster
- Resolved