[Bug] Dead lock error in Pulsar 3.0.

### 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 3.0.5 bookkeeper 4.16.

### Minimal reproduce step

has no idea yet.

### What did you expect to see?

Provide service for client.

### What did you see instead?

Can't produce or consume.

### Anything else?

The detailed stack is recorded at https://github.com/apache/bookkeeper/issues/4457.
As Pulsar 3.0 is the most popular version for users who want to follow up to the community branch, we select 3.0.5 and try to upgrade to it. While testing 3.0, we meet such a fatal error. I think it is worthwhile for us put in time to solve it.

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start by reading the detailed stack trace in apache/bookkeeper#4457 and reviewing the reported Pulsar 3.0.5 and BookKeeper 4.16 versions. Establish a reproducible case, then investigate the deadlock preventing clients from producing or consuming. Done means the service supports client production and consumption without the fatal error.

Written by the indexing model from the issue text.