On 23/08/17 13:48, Michael Vorburger wrote: > > Robert> Actually no. The backend side of things looks okay, as chains > are being > both closed and purged when requested from the frontend. I suspect > somebody is forgetting to close their transaction chains... > > Michael> Is a "transaction chain" the same as a transaction - the > objects returned from DataBroker's newReadWriteTransaction / > newReadWriteTransaction / newWriteOnlyTransaction? I did stumble upont > something - could https://git.opendaylight.org/gerrit/#/c/62196/ fix > this problem? Or is that unlikely to fix this OOM, but still a Good > Idea? Or doesn't matter to do cancel() if not submit() ?
'the same' in the sense that both are resources which need to be closed. So yes, it does matter that they are properly closed. > > > As far as I can see, with my still very limited understanding of mdsal > > internals, this does not seem to be the same as our earlier > > https://bugs.opendaylight.org/show_bug.cgi?id=8941 > <https://bugs.opendaylight.org/show_bug.cgi?id=8941> raised by > Stephen and > > fixed by Robert (which is being follow-up on in > > https://bugs.opendaylight.org/show_bug.cgi?id=9028 > <https://bugs.opendaylight.org/show_bug.cgi?id=9028> by Robert and > Tom) - > > does this initial quick analysis seem accurate to you? > > 9034 looks like 8941, except it's not transactions, but chains. I'll > cook up a prototype. > > > Thanks a lot !!! We'd love to out anything you come up with. As mentioned above, this is something else, so no patch coming from me righ tnow ;) Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
