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-2089 controller <p>As noted in <a href="https://jira.opendaylight.org/browse/CONTROLLER-2044" title="Improve sal-akka-raft serialization protocol" class="issue-link" data-issue-key="CONTROLLER-2044">CONTROLLER-2044</a> and <a href="https://jira.opendaylight.org/browse/CONTROLLER-2043" title="Circuit breaker timeout with BGP and tell-based protocol" class="issue-link" data-issue-key="CONTROLLER-2043">CONTROLLER-2043</a>, we have repeating writerUuid in the journal.</p> <p>Perusing akka.persistence, this value is used only for sanity checking in a filter &#8211; and that filter will happily live with just empty strings.</p> <p>On the write side, write a null String instead of writerUuid.<br/> On the read side, read the uuid, bump always report empty string.</p> <p>This should be a completely ABI compatible change.</p> CONTROLLER-2089

Do not store writerUuid in sal-akka-segmented-journal

Improvement Medium In Progress Unresolved Samuel Schneider Robert Varga pick-next pt Sun, 31 Dec 2023 12:43:07 +0000 Thu, 1 Feb 2024 08:38:04 +0000 7.0.12 8.0.5 9.0.1 clustering 0 1 <p>Yeah, except if we do that we do not pass the TCK.<br/> Looking at Cassandra, we need to store the writerUuid.</p> <p>So now we need another bit of state ... essentially we need to record the position at which the writerUuid changes. Then we need to remap them during adaptation.</p> Blocks CONTROLLER-2043 Issue split CONTROLLER-2044 Development Rank 0|i04747: