Does Couchbase Java SDK 3.3.0's shutdown hook reliably release Netty EventLoopGroups under high connection churn in containerized deployments?
Context Couchbase Java SDK 3.0–3.2.x leaked Netty EventLoopGroups when applications repeatedly created and closed Cluster instances without calling disconnect() . Version 3.3.0 added an automatic shutdown hook and improved cleanup in ClusterEnvironment to mitigate the leak. Uncertainty The shutdown hook relies on JVM shutdown hooks, which may not run when a