You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/07/09 17:37:53 UTC

[GitHub] [pulsar] merlimat commented on issue #4697: Memory leak in Pulsar 2.3.1

merlimat commented on issue #4697: Memory leak in Pulsar 2.3.1
URL: https://github.com/apache/pulsar/issues/4697#issuecomment-509736751
 
 
   @ArtemShaban the memory usage is due to the managed ledger write timeout that was introduced in 2.3. This has been disabled already by default in 2.4 release, along with a much more efficient implementation.
   
   The recommendation, with many topics, in 2.3 release would be to turn that off: 
   
   ```
   # Add entry timeout when broker tries to publish message to bookkeeper (0 to disable it).
   managedLedgerAddEntryTimeoutSeconds=0
   ```
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services