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
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> wrote:
> Hi, I recently switche
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/migra
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 wh
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
> "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 store
-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
There isn't any cluster-admin RPCs to defined new shards and migrate data.
You'd have to capture the data via REST from Beryllium and re-write it.
There is also a data import/export project but I'm not really familiar with
it.
On Fri, Mar 24, 2017 at 1:06 AM, Srini Seetharaman <
srini.seethara...@
...@lists.opendaylight.org
[mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom Pantelis
Sent: Friday, March 24, 2017 4:13 PM
To: Srini Seetharaman
Cc: controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Backward compatibility of akka-persistence journal
There isn'
t;
> 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 4:13 PM
> To: Srini Seetharaman
> Cc: controller-dev@lists.opendaylight.org
> From: controller-dev-boun...@lists.opendaylight.org
> > [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom
> > Pantelis
> > Sent: Friday, March 24, 2017 4:13 PM
> > To: Srini Seetharaman
> > Cc: controller-dev@lists.opendaylight.org
> >
>
>> > Regards
>> >
>> > Muthu
>> >
>> >
>> >
>> >
>> >
>> > From: controller-dev-boun...@lists.opendaylight.org
>> > [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom
>> > Pant
: Wednesday, March 29, 2017 7:31 AM
To: Tom Pantelis
Cc: Muthukumaran K; controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Backward compatibility of akka-persistence journal
When using module level sharding, it will be good if we can mention the
revision-date for the module in module
ent:* Wednesday, March 29, 2017 7:31 AM
> *To:* Tom Pantelis
> *Cc:* Muthukumaran K; controller-dev@lists.opendaylight.org
>
> *Subject:* Re: [controller-dev] Backward compatibility of
> akka-persistence journal
>
>
>
> When using module level sharding, it will be good if we can
14 matches
Mail list logo