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-1636 controller <p>DistributedShardedDOMDataTree service enables us to create distributed prefix-based shards. Current implementation relies on a special configuration shard where we store configuration for prefix-based shards. When we create a new distributed prefix-based shard, DistributedShardedDOMDataTree service updates this special configuration shard with new configuration and other nodes can react to this change, like create frontend for the new prefix-based shard etc.</p> <p>This special configuration shard is started upon DistributedShardedDOMDataTree service start and is created on all nodes specified in module-shards.conf (e.g. module-based entity-ownership shard is started similarly). Clearly with this approach we cannot support DistributedShardedDOMDataTree service on dynamically added cluster nodes (they don't have this special configuration shard replicated).</p> <p>We should not rely on static cluster nodes configuration from module-shards.conf and we should support DistributedShardedDOMDataTree service on dynamically added cluster nodes.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1636

DistributedShardedDOMDataTree should be able to work also with dynamically added cluster member nodes

Improvement Resolved Won't Do Unassigned Jakub Morvay Thu, 13 Apr 2017 12:41:29 +0000 Tue, 25 Jul 2023 08:24:30 +0000 Mon, 6 Sep 2021 09:00:14 +0000 clustering 0 0 <p>This component has been removed, hence we won't be addressing this.</p> Development External issue ID 8225 External issue URL Issue Type Rank 0|i02rsn: