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 2022/05/24 06:34:04 UTC

[GitHub] [pulsar] lhotari opened a new pull request, #15737: [Broker] Prevent the trigger running concurrently in the memory limit controller

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

   ### Motivation
   
   - under load, it's possible that the trigger immediately releases memory and causes the current
     usage to go under the limit while the trigger is executing. If a memory reservation call that exceed the limit occurs while the trigger is still executing, it would cause the trigger to be run even though the previous one is still executing. This scenario should be prevented.
   
   - the trigger was introduced in #15216
   
   ### Modifications
   
   - prevent the trigger being run concurrently


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [pulsar] lhotari merged pull request #15737: [Broker] Prevent the trigger running concurrently in the memory limit controller

Posted by GitBox <gi...@apache.org>.
lhotari merged PR #15737:
URL: https://github.com/apache/pulsar/pull/15737


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org