Congratulations!
-- --
??:
"dev"
https://github.com/apache/bookkeeper/pull/2788
I think this bug fix should be merged into 4.14.2
-- --
??:
"dev"
Thanks lot for you explanation.
sent from iPhone
-- Original --
From: Jack Vanlightly
my ack quorum is 1, please let me explain my confusion:
1??when one bookie is down, as you said, why some ledgers can be replicated
successfully, but some cannot.
2??from the code below in PendingReadLacOp, i don't see any codes relation to
ack quorum when read lac.
public void initiate() {
As title, When bookie is lost, the ledger which state is open cannot replicated
because of reading lac from failed bookie.
it would failed read lac from failed bookie, because it cannot be connected.
How bookkeeper auto recovery deal with open ledger in failed bookie ?
I don't know if it's a bug
Hello everyone,Now, decommission command need bookie stoped, and only
support one bookie at same time. I plan to make decommission behave more like
HDFS decommission commands: 1??support decommission two or more servers at
same time. 2??decommission will make servers become read-only. (m
Thanks for your explanation , I will go through this process, to check how to
avoid replicating ledger even when copy process gets started.
发自我的iPhone
-- Original --
From: Matteo Merli
Maybe the idea remove ledger from underreplicated when bookie
starts up has some problem, What important is, replicate legder puts so much
heavy loads on cluster. I want to reduce the affect.
suppose there are 5 copies and 4 bookies are lost, when one lost bookie is
online again, I don't
