Bug 963 - OSGi error in Topology manager component - After exiting 50/11450/2
authorJan Hajnar <jhajnar@cisco.com>
Tue, 16 Sep 2014 13:07:17 +0000 (15:07 +0200)
committerTony Tkacik <ttkacik@cisco.com>
Mon, 22 Sep 2014 21:20:23 +0000 (21:20 +0000)
commit602ff63c256c3f39dfb5d576b619c6cd5f9bfdc8
treec2ae48f244e70d4052fd2d184955087fc877c814
parentb495d88f63ba0b5b3959d7742ae683c869cf3ccc
Bug 963 - OSGi error in Topology manager component - After exiting
mininet of13 simulation

* added check in onLinkRemoved() to check if link exists before
atempting to delete it (without check, lots of datastore transaction
errors were displayed on mininet shutdown because links were already
removed with nodes)
* added checks to check if node, connector or link exists before trying
to remove it (reads are cheap and delete exception can break the
transaction chain)
* made reads synchronous
* added illegalState exception handling to operation processor
* made affected links removal to be in the same transaction as
Node/NodeConnector removal(creating and applying snapshot for each link
is expensive)
* updated tests

Change-Id: I83b5f91569e64082ce13a4f379cd6261e63fbde6
Signed-off-by: Jan Hajnar <jhajnar@cisco.com>
opendaylight/md-sal/topology-manager/src/main/java/org/opendaylight/md/controller/topology/manager/FlowCapableTopologyExporter.java
opendaylight/md-sal/topology-manager/src/main/java/org/opendaylight/md/controller/topology/manager/OperationProcessor.java
opendaylight/md-sal/topology-manager/src/test/java/org/opendaylight/md/controller/topology/manager/FlowCapableTopologyExporterTest.java