Description of problem: Running performance and scale tests to create neutron resources and stress ODL Oxygen with OpenStack Queens in an HA setup we observe several open transactions using Michael Vorburger's msdsal-trace tool. DataBroker : newWriteOnlyTransaction() 997x transactions opened here, which are not closed: (...) org.opendaylight.controller.md.sal.binding.impl.BindingDOMDataBrokerAdapter.newWriteOnlyTransaction(BindingDOMDataBrokerAdapter.java:69) (...) org.opendaylight.netvirt.neutronvpn.NeutronPortChangeListener.lambda$null$4(NeutronPortChangeListener.java:736) org.opendaylight.genius.infra.ManagedNewTransactionRunnerImpl.callWithNewWriteOnlyTransactionAndSubmit(ManagedNewTransactionRunnerImpl.java:45) org.opendaylight.netvirt.neutronvpn.NeutronPortChangeListener.lambda$handleNeutronPortUpdated$5(NeutronPortChangeListener.java:696) org.opendaylight.infrautils.jobcoordinator.internal.JobCoordinatorImpl$MainTask.runWithUncheckedExceptionLogging(JobCoordinatorImpl.java:416) org.opendaylight.infrautils.utils.concurrent.LoggingUncaughtThreadDeathContextRunnable.run(LoggingUncaughtThreadDeathContextRunnable.java:60) java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402) java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Version-Release number of selected component (if applicable): OSP 13 opendaylight-8.0.0-5.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Install OSP13 with ODL 2. Run scale tests using Browbeat 3. Actual results: Seeing open transactions Expected results: No open transactions Additional info:
Fixed by https://git.opendaylight.org/gerrit/71036 upstream, I’ll backport that to Oxygen and then to OSP.
Tested with puddle 2018-05-23.1 and opendaylight rpm opendaylight-8.0.0-10.el7ost.noarch . Could not reproduce. Verified that it has been fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086