Fix StandaloneFrontendHistory accounting 59/104959/6
authorŠimon Ukuš <simon.ukus@pantheon.tech>
Fri, 17 Mar 2023 08:58:40 +0000 (09:58 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Mon, 3 Apr 2023 17:11:36 +0000 (19:11 +0200)
commitf70fb5eaee514ffa5963049ac12286c2dee4ff80
tree7857dd00061d349c3c054dbfc8165cf1a755e98e
parentc45dbeced41db0fa006d12648f6c56e0a4be8f87
Fix StandaloneFrontendHistory accounting

testTransactionForwardedToLeaderAfterRetry() is exposing a scheduling
difference between the two implementations -- with tell-based protocol
we are holding off sending modifications until there is a significant
event needing them to be flushed to the backend.

Fixing this up exposes a bug in StandaloneFrontendHistory transaction
accounting, as circles back to ShardDataTree, where its transactions
are accounted for again -- fix that mistake by allocating transactions
directly in StandaloneFrontendHistory.

JIRA: CONTROLLER-2017
Change-Id: Ied00910f55bd3c63f99ae187396c1a193e5ece20
Signed-off-by: Šimon Ukuš <simon.ukus@pantheon.tech>
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/StandaloneFrontendHistory.java
opendaylight/md-sal/sal-distributed-datastore/src/test/java/org/opendaylight/controller/cluster/datastore/DistributedDataStoreRemotingIntegrationTest.java