lhotari commented on issue #22601: URL: https://github.com/apache/pulsar/issues/22601#issuecomment-2123954717
Looking up in Netty issue tracker. Found these issues that provide a lot of context: * https://github.com/netty/netty/issues/6184 * https://github.com/netty/netty/issues/2761 * https://github.com/netty/netty/issues/1865 * https://github.com/netty/netty/commit/a74149e9848fef73d909dd56843e0fbab23f877d * https://github.com/netty/netty/issues/1801 * https://github.com/netty/netty/issues/1797 * https://github.com/netty/netty/commit/6f79291d5bf7c515549234ed93dc00b84ce008c9 * https://github.com/netty/netty/issues/1925 It seems that this is a long time issue and it has been partially fixed. However, it's not fixed for many locations in the Netty code base and it's not safe to share ByteBuf instances in all cases. We need to find a workaround for the Pulsar use cases. In Pulsar, the sharing happens in this case at least via the broker cache ([RangeEntryCacheManagerImpl](https://github.com/apache/pulsar/blob/master/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/cache/RangeEntryCacheManagerImpl.java)) and the pending reads manager ([PendingReadsManager](org.apache.bookkeeper.mledger.impl.cache.PendingReadsManager)). -- 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]
