This group is locked. No changes can be made to the group while it is locked.
N Vivekanandan <n.vivekanandan@...>
We were contemplating to use v2 Driver for production after noticing that it has huge improvements over the v1 Driver.
Primarily in terms of its stability to use in HA active-active cluster when compared to v1 Driver which
is unstable for use in HA active-active clusters.
After going through available documentation, it looks v2 driver could have a couple of issues that could
occur in production deployments:
a. Journal DB unchecked explosion
- a situation where ODL is permanently disconnected from Openstack , but orchestrations are done in
Openstack Neutron continually successfully during this window. Could this end up with Journal DB overflowing,
And journal threads simply thrashing around between themselves to see if a resource-event can be posted to ODL?
b. Large number of journal threads (eg., each neutron-api-worker will have one or more ODL Journal thread fired) taking up
CPU cycles competing to address limited PENDING entries in the journal DB. These accesses (including Writes) can actually result in
DB performance drops.
There were ways attempted to restrict the number of journal threads in a process to just ‘one’ here:
But we are unsure what was concluded as the patch didn’t merge.
Is it possible to restrict the journal threads to just one per Neutron-API-Worker process through some other configuration.