Route {Journal,Snapshot}Protocol messages to DataPersistenceProvider 69/100769/1
authorRobert Varga <robert.varga@pantheon.tech>
Sun, 24 Apr 2022 11:17:15 +0000 (13:17 +0200)
committerRobert Varga <robert.varga@pantheon.tech>
Sun, 24 Apr 2022 11:17:53 +0000 (13:17 +0200)
commitd6d516aa953924121c3cf2a5bf9fd992b9c2b326
tree347a2b7acbd213baa371c253722714a35b288819
parentf01f64aab0fbcc383582bb211599b0cd09083111
Route {Journal,Snapshot}Protocol messages to DataPersistenceProvider

The way we wire our messages ends up being not exactly nice, as the
baseline RaftActor is not cognizant of all persistence operations. This
means it cannot correctly ignore responses to deletion of journal and
snapshot entries -- and hence we get dead letters logged.

Route JournalProtocol and SnapshotProtocol messages to
DataPersistenceProvider, which can then handle them and correctly
tell us whether to log them or not.

JIRA: CONTROLLER-2042
Change-Id: I47b8c3ae67d0a0ea0aad9f0a64e1bb8dc11400fc
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/RaftActor.java
opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/DataPersistenceProvider.java
opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/DelegatingPersistentDataProvider.java
opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/NonPersistentDataProvider.java
opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/PersistentDataProvider.java