https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-698 controller <p>The Data Store droptest does not work anymore, and these exceptions are seen when FRM is trying to write flows into the data store:</p> <p>java.lang.IllegalArgumentException: Metadata not available for modification [NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13} <p>], modificationType=SUBTREE_MODIFIED, childModification={(urn:opendaylight:inventory?revision=2013-08-19)node-connector=NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node-connector, modificationType=MERGE, childModification={(urn:opendaylight:inventory?revision=2013-08-19)node-connector[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13:4} <p>]=NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node-connector[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13:4} <p>], modificationType=WRITE, childModification={}]}]}]]<br/> at com.google.common.base.Preconditions.checkArgument(Preconditions.java:119) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.apply(SchemaAwareApplyOperation.java:186) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.NormalizedNodeContainerModificationStrategy.mutateChildren(NormalizedNodeContainerModificationStrategy.java:132) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.NormalizedNodeContainerModificationStrategy.applySubtreeChange(NormalizedNodeContainerModificationStrategy.java:163) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.NormalizedNodeContainerModificationStrategy$UnorderedMapModificationStrategy.applySubtreeChange(NormalizedNodeContainerModificationStrategy.java:311) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.apply(SchemaAwareApplyOperation.java:188) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.InMemoryDataTreeModification.resolveSnapshot(InMemoryDataTreeModification.java:110) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.yangtools.yang.data.impl.schema.tree.InMemoryDataTreeModification.readNode(InMemoryDataTreeModification.java:93) ~<span class="error">&#91;na:na&#93;</span><br/> at org.opendaylight.controller.md.sal.dom.store.impl.SnapshotBackedReadWriteTransaction.read(SnapshotBackedReadWriteTransaction.java:58) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMForwardedReadWriteTransaction.read(DOMForwardedReadWriteTransaction.java:51) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.md.sal.binding.impl.AbstractForwardedTransaction.doRead(AbstractForwardedTransaction.java:63) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.md.sal.binding.impl.BindingDataReadWriteTransactionImpl.read(BindingDataReadWriteTransactionImpl.java:31) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.md.inventory.manager.NodeChangeCommiter$4.applyOperation(NodeChangeCommiter.java:117) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.md.inventory.manager.FlowCapableInventoryProvider.run(FlowCapableInventoryProvider.java:93) <span class="error">&#91;bundlefile:na&#93;</span><br/> at java.lang.Thread.run(Thread.java:745) <span class="error">&#91;na:1.7.0_65&#93;</span><br/> 2014-08-17 01:41:01.330 PDT <span class="error">&#91;FlowCapableInventoryProvider&#93;</span> ERROR o.o.y.y.d.i.s.t.InMemoryDataTreeModification - Could not create snapshot for (urn:opendaylight:inventory?revision=2013-08-19)nodes/(urn:opendaylight:inventory?revision=2013-08-19)node/(urn:opendaylight:inventory?revision=2013-08-19)node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13} <p>]:NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13} <p>], modificationType=SUBTREE_MODIFIED, childModification={(urn:opendaylight:inventory?revision=2013-08-19)node-connector=NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node-connector, modificationType=MERGE, childModification={(urn:opendaylight:inventory?revision=2013-08-19)node-connector[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13:4} <p>]=NodeModification [identifier=(urn:opendaylight:inventory?revision=2013-08-19)node-connector[</p> {(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:13:4} <p>], modificationType=WRITE, childModification={}]}]}]</p> <p>To reproduce, simply run the cbench test with the Data Store loopback turned on (dropAllPackets on)</p> <p>Operating System: Mac OS<br/> Platform: Macintosh</p> CONTROLLER-698

Exceptions when Data Store droptest is running

Bug Resolved Won't Do Unassigned Jan Medved Sun, 17 Aug 2014 19:39:37 +0000 Thu, 19 Oct 2017 21:26:52 +0000 Mon, 9 Nov 2015 16:06:19 +0000 Helium mdsal 0 5 <p>Which Controller are you using?</p> <p>This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.</p> <p>I've retested this with the Lithium release and the issue is still there.<br/> with 57 iterations, the average performance value went from 20k to under<br/> 5k. Attached is a spreadsheet with this info.</p> <p>(In reply to Jamo Luhrsen from comment #3)<br/> &gt; I've retested this with the Lithium release and the issue is still there.<br/> &gt; with 57 iterations, the average performance value went from 20k to under<br/> &gt; 5k. Attached is a spreadsheet with this info.</p> <p>ignore this comment. was meant for another bug.</p> <p>Actually it was application error, which did not properly tracked its writes and causality between writes, using TransactionChain would introduce such causality.</p> Development External issue ID 1564 External issue URL Rank 0|i02m07: