[Bug] read entry failed cause No such ledger exists on Bookies with Orphan non-durable cursor

[ethqunzhong]

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

2.10.4

Minimal reproduce step

tmp

What did you expect to see?

tmp

What did you see instead?

1. I found that there are intermittent read request failures on 3 bookies in the cluster.

2. It can be seen from the logs, These read requests come from trying to read a non-existent ledger, and the ensemble for this ledger consists of these three bookies.
3. Related log as follows:
   
4. loop 3 in broker side.
   (This topic has no message in for a long time and no subscription.)

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!