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/CONTROLLER-1557 controller <p>Power off the virtual machine(Centos) when I was creating 100K entries with dsbenchmark test script which triggered snapshots with the config(shard-snapshot-batch-count=100) , and then restart the virtual machine, I found all snapshot files written just before power off showed a size of 0 bytes, finally the datastore recovery failed.</p> <p>This happened only in virtual machine environment but it was normal in physical host environment</p> <p>Operating System: Linux<br/> Platform: All</p> CONTROLLER-1557

Snapshot files showed a size of 0 bytes on restart after poweroff

Bug Resolved Won't Do Unassigned HeYunBo Wed, 12 Oct 2016 01:44:04 +0000 Thu, 19 Oct 2017 21:25:26 +0000 Fri, 28 Oct 2016 14:39:31 +0000 Lithium clustering 0 3 <p>This sounds like a problem in either the persistence provider or the filesystem itself. Moving to clustering component.</p> <p>I have consulted Akka community about this problem，They replied</p> <p>"What snapshot store are you using? The LocalSnapshotStore is only provided for use in tests/dev scenarios not for actual use in a production application."</p> <p>Actually，ODL is using LocalSnapshotStore provided for saving snapshot if didn't specify any snapshot-store in akka.conf.</p> <p>I think it's a file system problem，it sounds like the snapshot buffer didn't synchronize to the physical medium</p> <p>In addition，Akka also provided some plugins to Akka Persistence</p> <p><a href="http://akka.io/community/#plugins-to-akka-persistence" class="external-link" target="_blank" rel="nofollow noopener">http://akka.io/community/#plugins-to-akka-persistence</a></p> <p>These are related to database storage, I don't know how to choose and use</p> <p>We use the simple file-based local snapshot store by default. We can't use an external DB out-of-box, similar to the journal. Of course, users are free to choose a different persistent provider based on their needs.</p> <p>I agree this sounds like a file system buffering issue. Closing the bug...</p> <p>&gt; Closing the bug...</p> <p>I think INVALID is for closing reports bugs that are not really happening (typically user errors).</p> <p>Even if the real cause is in upstream (in this case the filesystem), ODL could still attempt to implement a workaround. And if we are not interested in implementing any workarounds, the correct state is WONTFIX.</p> Development External issue ID 6929 External issue URL Issue Type Rank 0|i02rb3: