This is the one of the approaches that you can downgrade.
But a general approach I mentioned in my previous is doing rollback via
re-replicating the data. Basically you can start a brand new bookie server
running with the old version that is configured using old disk format. Then
you can tear down
Il giorno lun 20 apr 2020 alle ore 11:49 Subash K
ha scritto:
> Thanks Enrico and Sijie, so I see the only way to rollback is not to use
> the new data format after upgrade. And once we change the data format, then
> we lose the option of rollback.
>
>
>
> And regarding “For the second question,
Il giorno lun 20 apr 2020 alle ore 09:20 Anup Ghatage
ha scritto:
> We are about 60% of the way done for all pending work for 4.11.
> So I agree with Sijie and give a +1 for 4.10.1
>
Sure
+1 for 4.10.1
Enrico
>
> Regards,
> Anup
>
>
> On Mon, Apr 20, 2020 at 12:18 AM Sijie Guo wrote:
>
> >
We are about 60% of the way done for all pending work for 4.11.
So I agree with Sijie and give a +1 for 4.10.1
Regards,
Anup
On Mon, Apr 20, 2020 at 12:18 AM Sijie Guo wrote:
> I think we can make 4.10.1 first?
>
> - Sijie
>
> On Sun, Apr 19, 2020 at 11:05 PM Enrico Olivelli
> wrote:
>
> > Al
I think we can make 4.10.1 first?
- Sijie
On Sun, Apr 19, 2020 at 11:05 PM Enrico Olivelli
wrote:
> Alessandro,
> Thanks for pointing this out.
>
> From my point of view these items are to be checked:
> - We have problems on Integration Tests (on GitHub Actions,
>
> https://github.com/apache/bo
+ users@ back to the discussion.
Sorry for being late to the discussion here.
When talking about "rollback" behavior, it usually involves two questions:
1) does wire protocol support rollback?
2) does data(metadata) format support rollback?
For the first question, the bookkeeper provides very g
