+1
Hang Chen 于2022年11月21日周一 20:03写道：
> Hi everyone,
> Please review and vote on the release candidate #0 for version 4.14.6,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your rev
+1
Yong Zhang 于2022年11月8日周二 09:09写道：
> +1
>
> Yong
>
> On Mon, 7 Nov 2022 at 20:58, Nicolò Boschi wrote:
>
> > +1
> > Nicolò Boschi
> >
> >
> > Il giorno lun 7 nov 2022 alle ore 08:50 Enrico Olivelli <
> > eolive...@gmail.com>
> > ha scritto:
> >
> > > +1
> > >
> > > Enrico
> > >
> > > Il giorn
+1
Thanks for your great work!
Thanks,
Lin
Max Xu 于2022年11月3日周四 21:45写道：
> +1
>
> Thanks for your great work!
>
> Best,
> Max Xu
>
>
> On Wed, Oct 26, 2022 at 9:24 AM Yong Zhang
> wrote:
>
> > Hi everyone,
> >
> > I want to discuss starting 4.15.3 release to including some
> > fixes/improveme
翻译邮件
对英语停用
Congratulations Steven!
Yong Zhang 于2022年10月15日周六 12:01写道：
> Congratulations Steven!
>
> Yong
>
> On Sat, 15 Oct 2022 at 03:32, Diego Salvi
> wrote:
>
> > Congratulations Steven!
> >
> > Diego Salvi
> >
> > Il giorno ven 14 ott 2022 alle ore 18:34 1060026287
> > <1060026...@qq.com.in
Hi Bookkeeper Community, I would like to start a VOTE on "Support data
migration."(BP-56)
Here is the design detail: https://github.com/apache/bookkeeper/issues/3456
and the discussion thread:
https://lists.apache.org/thread/0zlsm7z5j34j23gtlhf7rf72lfq62jyk
Thanks,
lordcheng10
Reply for Yong:
The migration tool is running in the recovery service. In addition, some
changes have been made to the migration tool, for more details, see issue and
PR:
issue: https://github.com/apache/bookkeeper/issues/3456
PR: https://github.com/apache/bookkeeper/pull/3457
Reply for Yong:
The migration tool is running in the recovery service.
In addition, some changes have been made to the migration tool, for more
details, see issue and PR:
The relevant descriptions are as follows:
??. Motivation
Currently bookkeeper does not support data migration, only data
Reply for Yong:
Q: Does the migration process run in the recovery service? Or run it
standalone?A: The migration tool is running in the recovery service.
In addition, some changes have been made to the migration tool, for more
details, see issue and PR:
issue: https://github.com/apache/bookkeep
Thanks for reviewing this PR!
Your comments is very good, I have fixed, PTAL, thanks!
After the discussion, I will start a VOTE!
Sorry for not describing the function of this BP clearly, this BP is not the
same as your proposal.
Because the current bookkeeper does not have the ability to migrate data and
can only perform data recovery, this BP mainly provides a data migration tool.
When bookkeeper has data migration to
How to use this data migration tool?
For example:
1. Migrate all ledger data on bookie1 and bookie2 to other bookie nodes:
sh bin/bookkeeper shell replicasMigration -bookieIds bookie1,bookie2 -ledgerIds
ALL -readOnly true
2. Migrate ledger1 and ledger3 on bookie1 and bookie2 to other bookie
The main content of this BP is for data migration, and the current title does
not match.
So I changed the corresponding issue and PR title to BP-56: Support data
migration
issue: https://github.com/apache/bookkeeper/issues/3456
PR: https://github.com/apache/bookkeeper/pull/3457
The corresponding issue and pr are as follows:
issue??https://github.com/apache/bookkeeper/issues/3456
PR??https://github.com/apache/bookkeeper/pull/3457
I made some modifications and implemented a replica data migration tool
### Motivation
We have a scenario where a large number of bookie nodes are offline, and we
find that the bookie's offline solution is very time-consuming.
Bookie offline steps are as follows:
1. Set the bookie node to be o
1.The first question, I don't understand what you mean, if it is an operation
error, which leads to the wrong writing of the offline node, there is no way to
avoid it.
The current offline command, if the operation is wrong, it may also be offline
to the wrong bookie node??
2.Before going offline
Hi Bookkeeper Community,
This is a BP discussion on Support non-stop bookie data migration and
bookie offline
The issue can be
found: https://github.com/apache/bookkeeper/issues/3456 ;
I copy the content here for convenience, any suggestions are welcome and
appreciated.
### Motivation
b
The 2-block cache sometimes affects the processing power of bookie. We have
encountered the problem of write failure because both caches are full. If the
write cache is increased, it will cause too much data in a flush, which will
lead to a longer time for a flush, and the cache resources cannot
The current write cache has only 2 blocks, which has the following deficiencies:
1.Insufficient use of cache: When half of the write cache
is flushed, it must wait for all the data in the write cache to be flushed
before it can be released. With the same write cache size, if we divide the
> In flushing
the write cache, it will trigger a checkpoint to mark the journal??s
lastMark position (100MB??s offset)
When flushing, only the lastMark value will be persisted to the file, but the
lastMark value will not be updated.
The lastMark value is updated only when the ForceWriteRequest c
I don??t know if I have described it clearly, for example:
Here is a bookkeeper cluster with 3 nodes (b1, b2, b3), and the corresponding
pulsar broker has 3 nodes (B1, B2, B3). When we restart the b1 and b2 nodes,
the pulsar broker will switch b1, b2 Put it in the excludeBookies collection
and i
I don??t know if I have described it clearly, for example:
Here is a bookkeeper cluster with 3 nodes (b1, b2, b3), and the corresponding
pulsar broker has 3 nodes (B1, B2, B3). When we restart the b1 and b2 nodes,
the pulsar broker will switch b1, b2 Put it in the excludeBookies collection
and i
I don??t know if I have described it clearly, for example:
Here is a bookkeeper cluster with 3 nodes (b1, b2, b3), and the corresponding
pulsar broker has 3 nodes (B1, B2, B3). When we restart the three nodes b1, b2,
and b3, the pulsar broker will Put b1, b2, and b3 into the excludeBookies
colle
91 bookie nodes.
When a bookie node restarts, it will cause the pulsar broker to put it into the
excludeBookies collection for isolation for 30 minutes. I reproduced it in the
test cluster:
-- --
??: "Enrico Olivelli"
Hi all,Recently I found a problem when upgrading pulsar and bookkeeper??
When upgrading bookkeeper, need to restart the bookie nodes in
turn. When restarting a bookie, the pulsar will fail to read and write to the
bookie, so as to isolate the bookie node. The default isolation is 30 minutes.
W
24 matches
Mail list logo
