Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[doc] Fix active memory metric name #2378

Merged
merged 1 commit into from
Jul 13, 2022
Merged

[doc] Fix active memory metric name #2378

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/asciidoc/faq.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,10 +102,9 @@ logger (`_reactor.netty5.channel.LeakDetection`) that helps to identify where th
or whether Reactor Netty already forwarded the ownership of the buffers to the application/framework.
By default, this logger is disabled. To enable it, increase the log level to `DEBUG`.

Another way to detect memory leaks is to monitor `reactor.netty5.bytebuf.allocator.active.heap.memory` and `reactor.netty5.bytebuf.allocator.active.direct.memory` meters:
Another way to detect memory leaks is to monitor `reactor.netty5.buffer.allocator.active.memory` meter:

- The `reactor.netty5.bytebuf.allocator.active.heap.memory` provides the actual bytes consumed by in-use buffers allocated from heap buffer pools
- The `reactor.netty5.bytebuf.allocator.active.direct.memory` provides the actual bytes consumed by in-use buffers allocated from direct buffer pools
- The `reactor.netty5.buffer.allocator.active.memory` provides the actual bytes consumed by in-use buffers allocated from the buffer pools

If the above meters are constantly growing, then it's likely that there is a buffer memory leak.

Expand Down