ovs-xapi-sync: Rerun processing when a db update arrives during a commit.
authorBen Pfaff <blp@nicira.com>
Thu, 8 Mar 2012 18:49:47 +0000 (10:49 -0800)
committerBen Pfaff <blp@nicira.com>
Thu, 8 Mar 2012 19:45:51 +0000 (11:45 -0800)
commit6c6b6b3f627d108d97011ca0f919a4a804d9ddce
tree7edf87410f4b8f8fb8f53b8abf37f6a126b444cc
parent4ce07c787650c63abd50da8aeb04045c01c4b8cd
ovs-xapi-sync: Rerun processing when a db update arrives during a commit.

The logic in ovs-xapi-sync didn't handle the case where ovsdb-server sends
a database update before it replies to a transaction that ovs-xapi-sync
sent, like this:

ovs-xapi-sync              ovsdb-server
-------------              ------------

                      .
                      .
                      .
transaction request  --->
                     <---  database contents update
                     <---  transaction reply
                      .
                      .
                      .

The update was not lost but ovs-xapi-sync would not process it until the
database changed again.

Bug #10082.
Reported-by: Krishna Miriyala <krishna@nicira.com>
Signed-off-by: Ben Pfaff <blp@nicira.com>
xenserver/usr_share_openvswitch_scripts_ovs-xapi-sync