wenbingshen edited a comment on issue #12169: URL: https://github.com/apache/pulsar/issues/12169#issuecomment-926602296
> @wenbingshen Do you have a chance to test with 2.8.1 ? That contains quite a few fixes, just to see if there's a difference. > > > producerRate: 880000000 > > I assume you are intentionally testing an overload situation? > > > After analyzing the pulsar broker heap dump, a large number of PendingAddOp instances have not been recycled or destroyed. > > That is probably expected if there's such a high load on the system. > > One possibility to protect from overload is to configure rate limiters on the system. > However, it would be good if the Pulsar system would have backpressure (even without rate limiting configured) to prevent the system getting into a state where it breaks because of OOM. One such improvement suggestion is documented in #10439 . @lhotari Thank you very much for your reply. I don’t know much about bookkeeper's back pressure mechanism and related parameters. I will learn this content later. In fact, here, the question I want to understand is: Keep the producerRate at 880000000, and perform the following four tests for the same traffic: 1. Configure maxMessagePublishBufferSizeInMB>0, OOM occurs when EWA=3:3:2 2. Configure maxMessagePublishBufferSizeInMB>0, OOM will not occur when EWA=3:3:3, 3:2:2, and 2:2:2 3. Configure maxMessagePublishBufferSizeInMB=-1, which is related to turning off the current limit, and OOM occurs when EWA=3:3:2 4. Configure maxMessagePublishBufferSizeInMB=-1, which is related to turning off the current limit. OOM will not occur when EWA=3:3:3, 3:2:2, and 2:2:2 Why compare 1 and 3, 2 and 4, the maxMessagePublishBufferSizeInMB parameter turns on or turns off the current limit, there is no effect, the test results of the two are the same, then what is the working meaning of maxMessagePublishBufferSizeInMB? -- 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]
