lhotari opened a new pull request, #18928:
URL: https://github.com/apache/pulsar/pull/18928

   Fixes #18927 
   
   ### Motivation
   
   There's a direct memory leak in RawReaderImpl, please see #18927 for details.
   
   ### Modifications
   
   Override methods 
org.apache.pulsar.client.impl.ConsumerBase#failPendingReceive and 
org.apache.pulsar.client.impl.ConsumerBase#clearIncomingMessages in 
org.apache.pulsar.client.impl.RawReaderImpl.RawConsumerImpl so that cleanup 
happens properly. Don't create RawMessageImpl instances in messageReceived 
method if consumer is already closing or closed.
   The changes should prevent future direct memory leaks caused by seeks or 
when the consumer is already closed.
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. Please attach the local 
preview screenshots (run `sh start.sh` at `pulsar/site2/website`) to your PR 
description, or else your PR might not get merged. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   
   ### Matching PR in forked repository
   
   PR in forked repository: <!-- ENTER URL HERE -->
   
   <!--
   After opening this PR, the build in apache/pulsar will fail and instructions 
will
   be provided for opening a PR in the PR author's forked repository.
   
   apache/pulsar pull requests should be first tested in your own fork since 
the 
   apache/pulsar CI based on GitHub Actions has constrained resources and quota.
   GitHub Actions provides separate quota for pull requests that are executed 
in 
   a forked repository.
   
   The tests will be run in the forked repository until all PR review comments 
have
   been handled, the tests pass and the PR is approved by a reviewer.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to