Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Error while reading ledger - ledger=13 - operation=Failed to read entry #23493

Open
2 of 3 tasks
kulame opened this issue Oct 21, 2024 · 3 comments
Open
2 of 3 tasks
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@kulame
Copy link

kulame commented Oct 21, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Read release policy

  • I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

pulsar 3.3.1

pulsar standalone

Minimal reproduce step

when i kill pulsar server, it can't restart.

What did you expect to see?

restart pulsar server successfully

What did you see instead?

errorllog

2024-10-21T13:22:37.107148+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,106+0000 [BookKeeperClientWorker-OrderedExecutor-0-0] ERROR org.apache.bookkeeper.proto.PerChannelBookieClient - Read for failed on bookie 172.31.86.237:38149 code EIO
2024-10-21T13:22:37.107845+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,107+0000 [BookKeeperClientWorker-OrderedExecutor-0-0] INFO  org.apache.bookkeeper.client.ReadOpBase - Error: Error while reading ledger while reading L13 E0 from bookie: 172.31.86.237:38149
2024-10-21T13:22:37.108054+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,107+0000 [BookKeeperClientWorker-OrderedExecutor-0-0] ERROR org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L13 E0-E0, Sent to [172.31.86.237:38149], Heard from [] : bitset = {}, Error = 'Error while reading ledger'. First unread entry is (-1, rc = null)
2024-10-21T13:22:37.108286+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,107+0000 [BookKeeperClientWorker-OrderedExecutor-0-0] WARN  org.apache.pulsar.broker.service.ServerCnx - [/127.0.0.1:43094][persistent://public/default/__change_events][__system_reader-reader-3eb78daeb6] Failed to create consumer: consumerId=4, Error while reading ledger -  ledger=13 - operation=Failed to read entry - entry=0
2024-10-21T13:22:37.108771+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,108+0000 [pulsar-io-18-4] WARN  org.apache.pulsar.client.impl.ClientCnx - [id: 0x4c2c9282, L:/127.0.0.1:43094 - R:localhost/127.0.0.1:6650] Received error from server: Error while reading ledger -  ledger=13 - operation=Failed to read entry - entry=0
2024-10-21T13:22:37.108954+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,108+0000 [pulsar-io-18-4] WARN  org.apache.pulsar.client.impl.ConsumerImpl - [persistent://public/default/__change_events][__system_reader-reader-3eb78daeb6] Failed to subscribe to topic on localhost/127.0.0.1:6650
2024-10-21T13:22:37.109045+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,108+0000 [pulsar-io-18-4] WARN  org.apache.pulsar.client.impl.ConnectionHandler - [persistent://public/default/__change_events] [__system_reader-reader-3eb78daeb6] Error connecting to broker: org.apache.pulsar.client.api.PulsarClientException: {"errorMsg":"Error while reading ledger -  ledger=13 - operation=Failed to read entry - entry=0","reqId":2435734987288602753, "remote":"localhost/127.0.0.1:6650", "local":"/127.0.0.1:43094"}
2024-10-21T13:22:37.109144+00:00 ip-172-31-86-237 pulsar[2304114]: 2024-10-21T13:22:37,109+0000 [pulsar-io-18-4] WARN  org.apache.pulsar.client.impl.ConnectionHandler - [persistent://public/default/__change_events] [__system_reader-reader-3eb78daeb6] Could not get connection to broker: org.apache.pulsar.client.api.PulsarClientException: {"errorMsg":"Error while reading ledger -  ledger=13 - operation=Failed to read entry - entry=0","reqId":2435734987288602753, "remote":"localhost/127.0.0.1:6650", "local":"/127.0.0.1:43094"} -- Will try again in 5.921 s

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@kulame kulame added the type/bug The PR fixed a bug or issue reported a bug label Oct 21, 2024
@lhotari
Copy link
Member

lhotari commented Oct 21, 2024

Minimal reproduce step

when i kill pulsar server, it can't restart.

@kulame Can you consistently reproduce this issue with a sequence of steps that someone else could perform to reproduce the issue?

  • Does this problem reproduce on Pulsar 3.3.2 ?
  • How about with PULSAR_STANDALONE_USE_ZOOKEEPER=1 environment variable? (Requires clean install to switch mode)

@kulame
Copy link
Author

kulame commented Oct 22, 2024

@lhotari i will try it.

@mawenyu
Copy link

mawenyu commented Oct 29, 2024

I use linux x64, java17, pulsar 3.0.4, pulsar c++ client 3.4.2, also face the same problem ; However, the problem is triggered when the storage node is powered off and restarted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

No branches or pull requests

3 participants