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-960 controller <p>When a client creates a transaction via one of the DOMDataBroker#new*Transaction, the broker automatically creates a corresponding DOMStore*Transaction instance in each logical data store (config and operational) although both may not be needed if the client doesn't actually perform an operation (read/put/merge/delete) on a logical data store. </p> <p>This creates unnecessary overhead for the transaction instance and the corresponding (essentially no-op) cohort on submit, particularly for the clustered data store. We can avoid this unnecessary overhead by lazily allocating the DOMStore*Transaction instances for a logical data store when and if the first operation is actually performed on that data store.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-960

Clustering: Minimize overhead of unused data store Tx instances on DOMDataBroker#new*Transaction

Bug Resolved Done Tom Pantelis Tom Pantelis Mon, 27 Oct 2014 15:38:23 +0000 Tue, 10 Mar 2015 15:31:43 +0000 Tue, 10 Mar 2015 15:31:43 +0000 Helium mdsal 0 3 <p>Submitted <a href="https://git.opendaylight.org/gerrit/#/c/12266/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/12266/</a></p> <p>As pointed out by Robert and Tony in the gerrit:</p> <p>This patch breaks consistency view between two logical datastores - as it was: DOM Broker transaction was snapshot in same time from both datastores, after this patch - DOM Broker transaction is snapshot in time when first type logical data store was accessed - this in reality changes behaviour of implementation in such way, that documented API Contract of DataBroker is not honnored and potentially it also breaks isolation between concurrent transactions.</p> <p>a = newReadWriteTransaction(); <br/> b = newReadWriteTranasction(); </p> <p>a.read(CONFIGURATION,PATH); // Returns null, PATH did not existed at time of allocation a and b.</p> <p>a.put(CONFIGURATION,PATH,foo); <br/> a.submit() // is submitted and committed.</p> <p>b.read(CONFIGURATION,PATH) == foo // Returns true, since backing TX was lazily allocated after a was submitted.</p> <p>I'll drop the patch.</p> <p>Instead I can make changes in the clustered data store to minimize the overhead of unused data store transactions.</p> <p>You still want to keep this open?</p> <p>Yeah - there's some objects created in the constructor that I think we do lazily. </p> <p>(In reply to Moiz Raja from comment #3)<br/> &gt; You still want to keep this open?</p> <p>Submitted <a href="https://git.opendaylight.org/gerrit/#/c/15859/1" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/15859/1</a></p> Development External issue ID 2260 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02nmf: