Description of problem: When using active/passive replication, ovsdb/replication.c uses "update" notifications, which means that the full change is sent across the wire instead of just the diffs. This is especially noticeable in the case of the "drop" port group (RFE for feature to allow removal here https://bugzilla.redhat.com/show_bug.cgi?id=1947807) and with Logical_Switches that have a lot of ports. In the former case, I've see 17000 entries in that port group that are sent during every single port create. Given the load we see on ovsdb-server, it seems like not having to iterate all of those objects to create/process those notifications would be helpful. Version-Release number of selected component (if applicable): FDP 21.C How reproducible: 100% Steps to Reproduce: 1. Set up active passive replication 2. Watch the update notifications between servers 3. Actual results: "update" notifications are sent Expected results: "update2" notifications are sent Additional info:
It's not a bug. Replication uses simple 'monitor' method and not a 'monitor_cond' therefore receives 'update' and not 'update2'. To change this, support for 'monitor_cond' method should be introduced to replication.c. This is a good change to have. Will be useful also for 2-Tier setup. For the implementation we might consider re-writing replication.c on top of ovsdb-cs module to avoid code duplication, but I'm not sure about that.
This bug did not meet the criteria for automatic migration and is being closed. If the issue remains, please open a new ticket in https://issues.redhat.com/browse/FDP