Client should be added to cache before we push the 55/19955/2
authorAnil Vishnoi <vishnoianil@gmail.com>
Fri, 8 May 2015 21:56:55 +0000 (03:26 +0530)
committerSam Hague <shague@redhat.com>
Fri, 8 May 2015 23:43:38 +0000 (23:43 +0000)
commit3521246b1c75d700e4479b00fa9a0dd241fbb936
treecb07094d62c01f8521f6df1e99a46b839222dac1
parentf396736ad8af9be19ed209572de9a5d8edb03312
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>
(cherry picked from commit 77af48ad9d278b2a7e6d54442bd23bff313e08ee)
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbConnectionInstance.java
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/OvsdbConnectionManager.java