> IMO, this is not expected behavior. In our test, both the client and > server's memory leak detection policy should be gotten from > `-Dio.netty.leakDetection.level` configuration instead of hard code as > `LeakDetectionPolicy.Paranoid`
Make sense. There are second level config for the memory detection. The first level is netty jvm param `-Dio.netty.leakDetection.level`, the second level is bookkeeper config `AbstractConfiguration#setAllocatorOutOfMemoryPolicy`. If the second level be config greater than `Disabled`, the second level will override the first level. If the second level is `Disabled`, we use the first level config.
