platinumhamburg opened a new issue, #2925: URL: https://github.com/apache/fluss/issues/2925
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version 0.9.0 (latest release) ### Please describe the bug 🐞 When a follower's ReplicaFetcherThread sends a fetchLog RPC to the leader and the call times out (via CompletableFuture.get(timeout, TimeUnit)), the pooled ByteBuf held by the late-arriving FetchLogResponse is never released. This causes Netty direct memory to grow indefinitely and never self-heal. Impact: - Each timed-out fetchLog RPC leaks one pooled ByteBuf - Under normal operation with occasional timeouts: slow leak - During leader OOM/restart causing mass timeouts: fast leak - Leaked buffers keep Netty PooledByteBufAllocator chunks alive permanently - Eventually triggers Old GC pressure when direct memory grows large, leading to a GC death spiral on affected nodes ### Solution _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
