Liu,
From your logs I see that the client is able to reach ZooKeeper, so I think
that createLedger should complete.
Are you sure that your program is not stuck at “addEntry” ?
Is your client machine able to connect to the bookies ?
You can dump the stacktrace of the JVM with jstack
I suggest
Dear All:
I can't create ledger using bookkeeper 4.10.0 version.
Below is my test code:
static String connectionString = "xxx.xxx.xxx.xxx:2181";
bkClient = new BookKeeper(connectionString);
byte[] password = "some-password".getBytes();
handle =
Ah sorry, it is my typo. the correct command is " bin/bookkeeper shell
-ledgeridformat long ledger -m [ledger-id]".
Prajakta, I understand you hit issues during bookie starts up. what I was
trying to help here is to guide you to use the tools to check the system.
Hope that can give enough
Could you elaborate a bit more on :
“
The Bookie handles both graceful stops and machine crashes without need of a
manual operation.
“
When a SIGTERM is issued to a bookie process, does any “shutdown” method get
invoked that would take care of doing the “data flush” as mentioned here:
Il giorno mar 3 dic 2019 alle ore 11:41 ha
scritto:
> Hi Bookkeeper Team,
>
>
>
> We’re currently running into an issue where on bookie restart it is not
> able to find certain entries in ledgers and hence reads for these entries
> keep failing.
>
> In most cases, the bookie is able to recover
Hi Bookkeeper Team,
We're currently running into an issue where on bookie restart it is not able to
find certain entries in ledgers and hence reads for these entries keep failing.
In most cases, the bookie is able to recover from these errors after a period
and things work as usual.
However, in
Sijie,
The command you had asked to run doesn't work. Pavan (adding him to this
thread) tried running it with "--ledgeridformat" as well, but that didn't work
either.
./bookkeeper shell ledger -ledgeridformat long -m 36
08:31:31,924 ERROR Error parsing command line arguments :
Sorry to digress a little bit from existing conversations here…..
But this issue is almost always noticed on bookie restart ….so wanted to
understand if this problem could be the result of unclean bookie shutdown….
In which case, what is the way to ensure a graceful termination of bookies, so
I mean the error "ERROR: invalid ledger id 56" is raised due to using a
wrong ledger id formatter. I was suggesting you rerunning the command to
collect more information so that we can debug.
- Sijie
On Tue, Dec 3, 2019 at 12:17 AM Sharda, Ravi wrote:
> Did you mean we should run this on a
Did you mean we should run this on a running environment to recover from the
failure?
“bin/bookkeeper shell ledger -ledgeridformat long -m [ledger-id]"
From: Sijie Guo
Sent: Tuesday, December 3, 2019 1:10 PM
To: Sharda, Ravi
Cc: Enrico Olivelli ; user ;
Flavio
10 matches
Mail list logo
