Amitabha Biswas <azbis...@gmail.com> wrote on 20/08/2016 08:14:36 AM:
> We have seen our Cloud deployment and usage come to a halt after > deleting a Logical Router, due the problem being addressed below. > The MAC_Bindings have a strong reference to the Datapath_Binding. > However the MAC_Bindings are never deleted anywhere, and when the > Datapath (associated with a MAC_Binding) is deleted, the ovsdb- > server returns Referential Integrity Violation. This prevents newer > operations initiated from the CMS (in our case OpenStack) from being > committed to the Southbound DB (the northd keeps getting the > violation for newer commits). > > Another way to avoid the Referential Integrity Violation in this > case is to make the datapath Column have a weak reference (default > is strong) to the Datapath_Binding row and allow the column to be > empty (min 0). We can probably add that on top of the current patch. > I?m making that assumption that it won?t affect the conditional > monitoring patch (791a7747427310f6a09c7b2f57a99d65338dfb45) which > introduced the Data_Binding column strong reference. > Yes it will work but I think that it is better to delete a MAC_Binding row when the logical port is deleted. There is no sense on keeping a MAC_Binding row of a deleted logical port. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
