Hi Tom, I assume using backup and restore for below scenario would still have the same issue right ? As I understand, Backup and Restore may make the content agnostic to the node-members but the data backed-up will still have the shard-level metadata as part of backed-up data which can impact restoration - I am assuming static shard configuration in this context
Regards Muthu From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom Pantelis Sent: Friday, March 24, 2017 10:27 AM To: Srini Seetharaman Cc: controller-dev@lists.opendaylight.org Subject: Re: [controller-dev] Backward compatibility of akka-persistence journal yes - module-shard.conf and modules.conf are still used, in Carbon as well. They specify the static shard and member configuration. The cluster admin RPCs can be used to dynamically add/remove shard replicas at which point the shard memberships are stored in the journal and the static configuration is no longer used. "instead of just relying on the default" - I assume you're referring to the default shard. All yang modules for which there isn't a shard specified in the .conf files are stored in the default shard. I suspect in your case the previous journal backup had the yang module in question stored in the default shard. However you had a specific shard defined in the .conf files so it went to that shard to read the data. The data in the default shard still exists and was restored but it just can't be accessed b/c reads/writes go to the specific shard. On Fri, Mar 24, 2017 at 12:37 AM, Srini Seetharaman <srini.seethara...@gmail.com<mailto:srini.seethara...@gmail.com>> wrote: My bad. The restore works fine once I remove the entries I made in module-shard.conf for the specific modules I am using. For some reason, having an entry blocks the restore. With Beryllium and Boron, do we still use the module-shard.conf and modules.conf? Is there a doc that gives more info on when to use it instead of just relying on the default? On Sun, Mar 19, 2017 at 10:29 AM, Srini Seetharaman <srini.seethara...@gmail.com<mailto:srini.seethara...@gmail.com>> wrote: Thanks Tom for the quick reply. Nothing shows up in the config datastore on warm restart with the old journal+snashot. I didn't see any error either. I can turn on debug mode and check. I'll also try the online restore and let you know. From this doc http://doc.akka.io/docs/akka/2.4/project/migration-guide-persistence-experimental-2.3.x-2.4.x.html it seemed no binary compatibility is offered for the journal. On Sunday, March 19, 2017, Tom Pantelis <tompante...@gmail.com<mailto:tompante...@gmail.com>> wrote: What doesn't work exactly? Is there an error? From what I recall I thought they were compatible wrt the journal schema but I could be wrong. You could use the online backup/restore. On Sun, Mar 19, 2017 at 12:50 PM, Srini Seetharaman <srini.seethara...@gmail.com<mailto:srini.seethara...@gmail.com>> wrote: Hi, I recently switched to using stable/boron that uses 2.4.7 akka version. I have an old backup of the journal and snapshot from beryllium-sr3. I noticed that restore of this backup to a boron cluster doesn't work. Perhaps because 2.3 experimental akka-persistence is not compatible with 2.4 akka-persistence. I wanted to confirm this. I also wanted to see if anyone has any ideas or workaround to import a journal+snapshot from beryllium onto boron. Thanks much! Srini. _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/controller-dev
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
