https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/DAEXIM-14 daexim <p>A daexim import really means overwriting the contents of the datastore, which is a large operation, which ends up being stored in journal.</p> <p>Doing multiple consecutive imports can cause the journal to grow, consuming both on-disk (leveldb file) space and in-memory (heap) space.</p> <p>Add an option whereby after a successful import the CDS leader is instructed to take a snapshot, hence purging the now-stale journal entries – controlling consumption of both resources.</p> DAEXIM-14

Add an option to trigger a CDS snapshot after import

New Feature Medium Confirmed Unresolved Tibor Král Robert Varga Thu, 12 Sep 2019 17:52:30 +0000 Fri, 8 Dec 2023 17:04:16 +0000 General 0 2 <p>Full import in most databases is done with integrity and transaction support off during import and some (optional) checks at the end when the indexes are being rebuilt.</p> <p>IMHO taking the snapshot after import is treating the symptom instead of fixing the underlying issue that import is pumping all the data through the normal transaction engine and there is no way to turn on/off appropriate import knobs in it.</p> Relates CONTROLLER-1913 Development Rank 0|i03p0f: