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-1950 controller <p>When writing data to path "/" it is written only to default shard without affecting the others.</p> <p>Picture this:<br/> We want to replicate primary site to secondary. The primary contains data in 3 shards- topology, inventory and default. <br/> Getting this state and writing it to the secondary datastore will write everything only to the default shard (even though there is data which should be written to different shards). <br/> Furthermore if the secondary datastore contained any data in those other shards, this data won't be overwritten. </p> <p>Committing WRITE transaction to the ROOT (path "/") should delete everything and then correctly write the data to the right shards. So that after the write succeeds the datastore only contains the written data.</p> CONTROLLER-1950

CDS frontend incorrectly handles root overwrite with multiple shards

Bug High Resolved Done Robert Varga Tibor Král Thu, 25 Jun 2020 13:00:04 +0000 Fri, 26 Jun 2020 21:22:07 +0000 Fri, 26 Jun 2020 21:22:07 +0000 Magnesium SR2 Sodium SR4 2.0.3 clustering 0 2 <p>This is a failure on part of CDS – if there are multiple shards and the write target is YangInstanceIdentifier.empty(), it needs to split the data being written according to the sharding strategy.</p> <p>This is a counterpart to <a href="https://jira.opendaylight.org/browse/CONTROLLER-1932" title="Provide support for Root DTCL reacting to all modifications even in sharded datastore" class="issue-link" data-issue-key="CONTROLLER-1932"><del>CONTROLLER-1932</del></a> and complements the logic done in the read() path.</p> <p>This essentially means that neither merge(), write(), nor delete() paths in TransactionProxy do the right thing with respect to module-based shard splitting. Note how the read() path is handled, simply because that is required for NETCONF.</p> <p>In the modification paths, though:</p> <ul> <li>delete() has to issue delete() to all shards</li> <li>merge() need to traverse each data child, lookup the correct shard, create per-shard ContainerNodes for each touched shard and issue merge() to</li> <li>write() is a combination of delete and merge: i.e. create ContainerNodes for <b>all</b> shards and issue write() to all of them (even if the container is empty)</li> </ul> <p> </p> Relates CONTROLLER-1951 CONTROLLER-1913 CONTROLLER-1932 Development Rank 0|i03tb3: