All- I bumped into the following while trying to persist the logical flow information in ovn-controller:
When OVSDB change tracking is turned on, sequence numbers are generated for each row delete event. However, the memory the row uses is freed anyway, so code that is looping through tracked changes has no way to determine *which* row has been deleted. This admits of three rather nasty solutions that immediately come to mind: (1) keep a copy of the row information around (which amounts to a memory leak - ugh) (2) if you are trying to persist data and you hit a delete event, do some variation of "flush the persisted data and rebuild the table from scratch", which begs the question if the data is *really* persisted... (3) replace ovsdb... Ryan (regXboi)
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
