Code Review / ovsdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a2cb76d) | patch
Anil noticed there was a race condition here where we might write 88/20188/6
authorEd Warnicke <hagbard@gmail.com>
Tue, 12 May 2015 22:27:11 +0000 (15:27 -0700)
committerEd Warnicke <hagbard@gmail.com>
Tue, 12 May 2015 23:35:09 +0000 (23:35 +0000)
commit0606a8568104b342c7a7f2b33b05fdde1315bac5
tree5972a41b0a6d60e1c3854810bc29b62b08b83273tree | snapshot
parenta2cb76d0900c840846ef216b6593bc4df259f429commit | diff
Anil noticed there was a race condition here where we might write
an ovsdb-node to the operatational store before recording the
TransactInvoker we needed for people to be able to use it to write to
ovsdb.  This fixes that by imposing the order:

1)  Record the TransactInvoke for the ovsdb-node (internally)
2)  Write the ovsdb-node to OPER
3)  Register callbacks for monitors from ovsdb

Change-Id: I55202678521065b1a8c2f018a9f229b6be263a48
Signed-off-by: Ed Warnicke <hagbard@gmail.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbConnectionInstance.java diff | blob | history
Open vSwitch Database Management Protocol