[Bug] org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: ManagedCursor not found
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Read release policy
- [X] 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 2.8.1
### Minimal reproduce step
zk full GC




zk 挂掉后,导致
borker无法与bookie建立连接
### What did you expect to see?
question1: why zookeeper full gc?
question2: why broker not connect bookie?
### What did you see instead?
I don't know to troubleshoot
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start with the reported Pulsar 2.8.1 reproduction: ZooKeeper full GC, the ManagedCursor-not-found exception, and the broker-to-bookie connection failure. Reproduce or inspect the attached logs and screenshots to establish why ZooKeeper enters full GC and why the broker cannot connect to the bookie; done means both causes and a verified fix or documented resolution are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100