[Bug][Java client] Possible race condition in closing consumer which causes a leak in memory limit controller and direct memory with pooled messages

[lhotari]

Search before asking

• I searched in the issues and found nothing similar.

Version

master

Minimal reproduce step

This was an issue that came up in PR review comment #18928 (comment)

What did you expect to see?

There shouldn't be a race between org.apache.pulsar.client.impl.ConsumerImpl#closeAsync and org.apache.pulsar.client.impl.ConsumerImpl#messageReceived .

What did you see instead?

It's possible that closeAsync and messageReceived are in a race and incoming messages don't get properly cleaned up. This can cause a leak in the memory limit controller and also leak direct memory.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[github-actions]

The issue had no activity for 30 days, mark with Stale label.