I checked your issue on master with Sodium opendaylight.
I had no big journaldb, as it is only a test environment.
First what is important: if opendaylight is dead and neutron API is used than the journal will contain more and more entries.
What I expect is that after restarting opendaylight:
* if I do something on the API the journal is synced towards opendaylight. For me this worked.
* after maintenance_interval (300sec by default under ml2_odl confing section) the contents of the journal should be synced towards opendaylight. For some reason this one is not working.
I check how to fix the periodic sync, but as a workaround could you please check if any request on neutron API (after starting again opendaylight creating a network or port) starts the sync?
I checked your issue on master with Sodium opendaylight.
I had no big journaldb, as it is only a test environment.
First what is important: if opendaylight is dead and neutron API is used than the journal will contain more and more entries.
What I expect is that after restarting opendaylight: interval (300sec by default under ml2_odl confing section) the contents of the journal should be synced towards opendaylight. For some reason this one is not working.
* if I do something on the API the journal is synced towards opendaylight. For me this worked.
* after maintenance_
I check how to fix the periodic sync, but as a workaround could you please check if any request on neutron API (after starting again opendaylight creating a network or port) starts the sync?