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-1318 controller <p>Currently we prepend the shard's persistent ID with the member role name. This presents a couple drawbacks: </p> <p>1) you can’t change the member name or the shard data wont be recovered from persistence on restart.</p> <p>2) you can’t backup a journal on one node and restore it on another node. </p> <p>We should omit the member role name and/or allow for the persistence ID to be specified in the module-shards file.</p> <p>To preserve data for existing installations we'll need to migrate the existing persisted shard data to the new persistent ID.</p> <p>Note: we need to keep the member role name as part of the shard name as we use that to identify the raft peers.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1318

Clustering: Remove the member role name from the shard's persistent ID

Bug Resolved Won't Do Kalaiselvi Tom Pantelis Wed, 13 May 2015 18:29:23 +0000 Mon, 18 Jan 2016 08:40:52 +0000 Mon, 18 Jan 2016 08:40:52 +0000 Post-Helium clustering 0 2 <p>This has impact on backwards compatibility.</p> <p>#2 is no longer an issue with the Be online backup feature which takes an in-memory data tree snapshot and thus isn't dependent on akka persistence. So an online backup can be restored on any node.</p> <p>If a use case arises for changing the member name then we could add an RPC to do so. The change would have to be propagated to all nodes in the cluster (as a server config change).</p> <p>I'm closing this bug.</p> Development External issue ID 3211 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02ptz: