Comment 5 for bug 1996594

The ovs python library does not have support for RAFTs update3/monitor_cond_since primitives before 2.17. This means that every disconnect (which as you point out can happen with every leadership election on leader-only connections), involves syncing all db data to the client. This is untenable on a large production deployment. With update3/monitor_cond_since, a reconnect will only have to pull any transactions that were missed while it was disconnected.

There are several patches and fixes related to adding update3/monitor_cond_since support and the ovs team declined to backport them. So it is an extremely bad idea to try to use RAFT w/ openstack w/ anything earlier than ovs 2.17.