>You should start a new bookie with the new configuration.
If the DirectEntryLogger needs to set up a separate bookie service, it
would be hard for users to switch from the DefaultEntryLogger to
DriectEntryLogger.
>It is not generally possible to guarantee compatibility between different
> You should never do this in production.
But the user may not know the limitation, they may believe that the switching
is compatible, not introduce some problems.
> BTW do you have a possible solution?
see https://github.com/apache/bookkeeper/pull/4041
Il giorno lun 31 lug 2023 alle ore 02:40 Yan Zhao
ha scritto:
>
> I am concerned about a possible scenario where a user tries to use DirectIO,
> runs it for a period of time, and experiences some problem on the bookie
> server side, but is unsure of the cause and suspects it may be related to
I am concerned about a possible scenario where a user tries to use DirectIO,
runs it for a period of time, and experiences some problem on the bookie server
side, but is unsure of the cause and suspects it may be related to DirectIO. As
a result, the user disables DirectIO and restarts. In this
I think that you should not do this kind of things.
You should start a new bookie with the new configuration.
It is not generally possible to guarantee compatibility between different
implementations.
I tend to close the case as 'won't fix'
Enrico
Il Dom 30 Lug 2023, 13:00 horizonzy ha
