sijie commented on a change in pull request #6178: Introduce maxMessagePublishBufferSizeInMB configuration to avoid broker OOM URL: https://github.com/apache/pulsar/pull/6178#discussion_r379166541
########## File path: conf/broker.conf ########## @@ -324,6 +324,18 @@ replicatedSubscriptionsSnapshotTimeoutSeconds=30 # Max number of snapshot to be cached per subscription. replicatedSubscriptionsSnapshotMaxCachedPerSubscription=10 +# Max memory size for broker handling messages sending from producers. +# If the processing message size exceed this value, broker will stop read data +# from the connection. The processing messages means messages are sends to broker +# but broker have not send response to client, usually waiting to write to bookies. +# It's shared across all the topics running in the same broker. +# Use -1 to disable the memory limitation. Default is 1/5 of direct memory. +maxMessagePublishBufferSizeInMB= + +# Interval between checks to see if message publish buffer size is exceed the max message publish buffer size +# Use 0 or negative number to disable the max publish buffer limiting. +messagePublishBufferCheckIntervalInMills=100 Review comment: ```suggestion messagePublishBufferCheckIntervalInMillis=100 ``` ---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
