lhotari commented on issue #10433: URL: https://github.com/apache/pulsar/issues/10433#issuecomment-830017705
Since the reported problem could be related to Netty Recycler usage, I'd recommend doing the testing with Netty Recycler completely turned off (this was already proposed in the first comment). 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. @dinghram Would you be able to run your CHO (Continuous Hours of Operation) tests with Pulsar configured with `-Dio.netty.recycler.maxCapacityPerThread=0` ? It would be very useful if you could also share the possible impact to performance (throughput, latency, resource utilization) after disabling Netty Recycler by setting `-Dio.netty.recycler.maxCapacityPerThread=0` (in `PULSAR_EXTRA_OPTS` as explained [in the first comment](https://github.com/apache/pulsar/issues/10433#issuecomment-828953935)). -- 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]
