Skip to content

Conversation

@tomyouyou
Copy link
Contributor

@tomyouyou tomyouyou commented Jul 22, 2025

…olumn when there are connections

mgmt_db: 0.0 gb (0.0 %)

File Descriptors

Total: 0, limit: 65438

Free Disk Space

Low free disk space watermark: 1.0 gb
Free disk space: 49.202 gb

Totals

Connection count: 127
Queue count: 632
Virtual host count: 1

Listeners

Interface: [2001:123::2], port: 25672, protocol: clustering,

Proposed Changes

Please describe the big picture of your changes here to communicate to the RabbitMQ team why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.

A pull request that doesn't explain why the change was made has a much lower chance of being accepted.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

Checklist

Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally with my changes
  • If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
  • If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

Further Comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution
you did and what alternatives you considered, etc.

…olumn when there are connections

mgmt_db: 0.0 gb (0.0 %)
reserved_unallocated: 0.0 gb (0.0 %)

File Descriptors

Total: 0, limit: 89903

Free Disk Space

Low free disk space watermark: 1.0 gb
Free disk space: 40.0079 gb

Totals

Connection count: 1
Queue count: 3
Virtual host count: 1

Listeners

Interface: [2001:123::2], port: 25672, protocol: clustering,
@mkuratczyk
Copy link
Contributor

Almost all components moved away from using the file_handle_cache (it will go away completely), so the value it returns will be very low or zero already, it definitely won't be the actual number of FDs in use by RabbitMQ. File descriptor usage can be monitored externally, on the operating-system level.

@mkuratczyk mkuratczyk closed this Jul 22, 2025
@michaelklishin
Copy link
Collaborator

Relevant doc guide: Infrastructure and Kernel Metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants