er: Dump ledger index entries into readable format.
> usage: ledger [-m]
>
>
> --
> *From:* Belgundi, Prajakta
> *Sent:* Tuesday, December 3, 2019 2:03 PM
> *To:* user@bookkeeper.apache.org
> *Cc:* Enrico Olivelli ; Flavio Junqueira <
> f...@apache.org>; Sharda
ge: ledger [-m]
From: Belgundi, Prajakta
Sent: Tuesday, December 3, 2019 2:03 PM
To: user@bookkeeper.apache.org
Cc: Enrico Olivelli ; Flavio Junqueira ;
Sharda, Ravi
Subject: RE: Bookeeper exception on pods restart
Sorry to digress a little bit fro
we don’t lose/corrupt any data?
-Thanks,
Prajakta
From: Sijie Guo
Sent: Tuesday, December 3, 2019 1:53 PM
To: Sharda, Ravi
Cc: Belgundi, Prajakta; Enrico Olivelli; user; Flavio Junqueira
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
I mean the error "ERROR: invalid ledg
elli ; user <
> user@bookkeeper.apache.org>; Flavio Junqueira
> *Subject:* Re: Bookeeper exception on pods restart
>
>
> [EXTERNAL EMAIL]
> I think 4.7.2 is using UUID as the ledger id formatter by default (it was
> a mistake, and reverted in its subsequent releases).
>
lavio Junqueira
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
I think 4.7.2 is using UUID as the ledger id formatter by default (it was a
mistake, and reverted in its subsequent releases).
So you might have to run “bin/bookkeeper shell ledger -ledgeridformat long -m
[ledg
--
> *From:* Enrico Olivelli
> *Sent:* Monday, December 2, 2019 7:01 PM
> *To:* user
> *Cc:* Sijie Guo ; Flavio Junqueira
> *Subject:* Re: Bookeeper exception on pods restart
>
>
> [EXTERNAL EMAIL]
>
>
> sh-4.2# ./bookkeeper shell ledger -m
ledger 728
From: Enrico Olivelli
Sent: Monday, December 2, 2019 7:01 PM
To: user
Cc: Sijie Guo ; Flavio Junqueira
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
sh-4.2# ./bookkeeper shell ledger -m 56
ERROR: invalid ledger id 56
ledger: Dump
age: ledger [-m]
> -m,--meta Print meta information
> --
> *From:* Sijie Guo
> *Sent:* Friday, November 29, 2019 3:15 PM
> *To:* Sharda, Ravi
> *Cc:* user ; Flavio Junqueira
> *Subject:* Re: Bookeeper exception on pods restart
>
>
> [EXTERNAL EMAIL]
> Sorry
Hello Sijie,
Any luck with this? Please let us know what could be going wrong.
Thanks & best regards,
Ravi
From: Sharda, Ravi
Sent: Friday, November 29, 2019 3:28 PM
To: Sijie Guo
Cc: user ; Flavio Junqueira
Subject: Re: Bookeeper exception on pods res
le exists. Attaching the output
> of "ls -R -L", instead.
>
> --
> *From:* Sijie Guo
> *Sent:* Friday, November 29, 2019 2:31 PM
> *To:* Sharda, Ravi
> *Cc:* user ; Flavio Junqueira
> *Subject:* Re: Bookeeper exception on pod
resolve itself when
auto-replication runs??
-Thanks,
Prajakta
From: Enrico Olivelli - Diennea
Sent: Thursday, November 28, 2019 6:11 PM
To: user@bookkeeper.apache.org
Cc: f...@apache.org
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
I don’t think there is a good value.
Yo
@bookkeeper.apache.org
Cc: f...@apache.org
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
I don’t think there is a good value.
You can use WriteQuorumSize = AckQuorumSize, this way you will see an error on
the writing client in case of write failure to any of the bookies
Usually you are enabling
ecommend, so we
never see this?
What other ledger creation parameters do you need information about?
-Thanks,
Prajakta
From: Enrico Olivelli - Diennea
Sent: Thursday, November 28, 2019 5:19 PM
To: user@bookkeeper.apache.org
Cc: f...@apache.org
Subject: Re: Bookeeper exception on pods restart
...@apache.org
Subject: Re: Bookeeper exception on pods restart
[EXTERNAL EMAIL]
Hi Prajakta,
What ledger creation parameters are you using ? Ensamble size, Write quorum
size, Ack quorum size ?
If ackQuorumSize < WriteQuorumSize it is possible that a write to the bookie
failed and e
Hi Prajakta,
What ledger creation parameters are you using ? Ensamble size, Write quorum
size, Ack quorum size ?
If ackQuorumSize < WriteQuorumSize it is possible that a write to the bookie
failed and even if the entry is supposed to be on the bookie it never reached
it but the overall single
Hello Team,
We have a question about an issue we are running into with Bookeeper.
We use bookkeeper version 4.7.3.
This issue occurs occasionally when Bookkeeper servers are restarted.
We see the following error in the logs for some time, which blocks Pravega's
operations for the same duration.
16 matches
Mail list logo
