-
Bug
-
Resolution: Done
-
None
-
Carbon
-
None
-
Operating System: All
Platform: All
-
9028
The fix for CONTROLLER-1746 exposes a problem with RaftActor, where the sequencing of applied state is violated and the same journal entry is being applied – leading to violation of transaction ordering in DataTree.
This is readily reproduced in https://jenkins.opendaylight.org/releng/view/netvirt/job/netvirt-csit-3node-openstack-ocata-gate-stateful-carbon/ and we saw this happening with Cluster Singleton Service – at high transition rates EOS blows up on the same problem.
- blocks
-
CONTROLLER-1756 OOM due to huge Map in ShardDataTree
- Resolved
-
CONTROLLER-1762 ODL is up and ports are listening but not functional
- Resolved
-
CONTROLLER-1763 On restarting ODL on one node, ODL on another node dies in a clustered setup
- Resolved
-
MDSAL-275 VerifyException from flapping service singleton registration
- Resolved
- is duplicated by
-
CONTROLLER-1761 Uncaught error from thread ... shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled
- Resolved