lhotari commented on issue #10136: URL: https://github.com/apache/pulsar/issues/10136#issuecomment-830023071
Since there's also a possibility that the reported problem could be related to Netty Recycler usage, I'd recommend doing the testing with Netty Recycler completely turned off. You can find positive reports about disabling the Netty Recycler at https://github.com/netty/netty/pull/5968#issuecomment-399578989 and https://github.com/netty/netty/pull/5968#issuecomment-352823429 . Elasticsearch [also disabled Netty Recycler completely](https://github.com/elastic/elasticsearch/blob/5baabff6670a8ed49297488ca8cac8ec12a2078d/distribution/tools/launchers/src/main/java/org/elasticsearch/tools/launchers/SystemJvmOptions.java#L50) because of the problems it causes. Here's an example of the recommended options to set in `PULSAR_EXTRA_OPTS`: ``` broker: configData: PULSAR_EXTRA_OPTS: -Dio.netty.recycler.maxCapacityPerThread=0 -Dpulsar.allocator.leak_detection=Simple -Dpulsar.allocator.exit_on_oom=true ``` It would be very useful if you could also share the possible impact to performance (throughput, latency, resource utilization) after disabling Netty Recycler with the setting described above. -- 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]
