Client should be added to cache before we push the 56/19956/1
authorAnil Vishnoi <vishnoianil@gmail.com>
Fri, 8 May 2015 21:56:55 +0000 (03:26 +0530)
committerAnil Vishnoi <vishnoianil@gmail.com>
Fri, 8 May 2015 22:03:51 +0000 (03:33 +0530)
commit77af48ad9d278b2a7e6d54442bd23bff313e08ee
tree863f4447b744b5936d79991650c4abf8d2d009e3
parent58e83ca86374deb866ced488754dfa574fd9bd47
Client should be added to cache before we push the
info(OvsdbNodeAugmentation) to operational data store.
With the existing implementation we were putting task
in invoker queue to dump the data to operational data
store and then registtering for the connection callback.
After that it's adding client to cache. So if invoker
writes the data to operational data store before
it adds client to cache, any code listening to
OvsdbNodeAugmentaiton, might not be able to do any
operation if that key is not there in connection
manager cache. It works if invoker loose the race
of putting data to operational data store, it fails if
it succeed.

Change-Id: Ic73c5b7bbe0f94b04bf932b67b872099f2c27b5c
Signed-off-by: Anil Vishnoi <vishnoianil@gmail.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbConnectionInstance.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbConnectionManager.java