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-911 controller <p>Operational data does not need to be persisted. We should therefore be able to disable persistence for the whole operational datastore or a maybe even specific shards so that we can use this as a means to optimize performance.</p> <p>Currently we persist by default to ensure that when a node is restarted it can restore it's state from disk and subsequently get synced up with the Leader. If we do not restore the state from disk the complete state will be replicated from the leader. We need to ensure that replicating the whole state of a shard is fast enough so that using replication vs persistence for recovery does not have an adverse effect on performance.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-911

Clustering : Make persistence configurable at the datastore or shard level

Bug Resolved Done Moiz Raja Moiz Raja Thu, 2 Oct 2014 20:31:31 +0000 Mon, 25 May 2020 17:40:51 +0000 Fri, 31 Oct 2014 12:56:11 +0000 Helium mdsal 0 3 <p>1. When starting up check if persistence is enabled. If it is not do not recover from disk.<br/> 2. On recovery when the journal is empty the Leader should send complete state to the follower instead of checking for log entries.<br/> 3. Replication should work even when persistence if turned off.<br/> 4. Configurable using config subsystem. For Helium-1 this will only be at the datastore level.</p> <p>The original idea was to use a an in-memory journal/snapshot store when persistence was not enabled. That may not work however because currently you can have only one journal/snapshot store per actor system. See <a href="https://groups.google.com/forum/#!topic/akka-user/8Vlf6UonURo" class="external-link" target="_blank" rel="nofollow noopener">https://groups.google.com/forum/#!topic/akka-user/8Vlf6UonURo</a>.</p> <p>Since persistence plugins are configurable only at the actor system level it looks like we will need to create a separate actor system for the config datastore. This actor system will use an inmmemory-journal/snapshot store for pllugins. The rest of the design stays as is.</p> <p>Finally went with conditionally turning persistence on and off on the Shard/RaftActor</p> Duplicate CONTROLLER-871 CONTROLLER-1916 Development External issue ID 2134 External issue URL ODL SR Target Milestone Rank 0|i02nbj: