Bug 963 - OSGi error in Topology manager component - After exiting 33/11233/6
authorJan Hajnar <jhajnar@cisco.com>
Tue, 16 Sep 2014 13:07:17 +0000 (15:07 +0200)
committerJan Hajnar <jhajnar@cisco.com>
Sun, 21 Sep 2014 23:42:13 +0000 (01:42 +0200)
commit09563b7786e591a8faaf1947a1fb27b8183414f2
tree529ec6cbbaa19cb12c22734428b97118bcd8f599
parent6b747e78e4cfef9ab3b0a908589d8ddb17eed7d8
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: Icef03a02bbfb88a7cebd0fe35e4b713dcfeb317c
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