-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Node Exporter leaving OPENFILE marker on pvc host paths #2795
Comments
Are these mountpoints btrfs, by any chance? |
Sort of. The volumes themselves are XFS/EXT4. But with the storage solution we use, the backend blocks get written to a PURE device through a btrfs filesystem that is mounted on the nodes. |
You are possibly hitting #2772. Can you try disabling the btrfs collector temporarily? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Host operating system: output of
uname -a
node_exporter version: output of
node_exporter --version
node_exporter command line flags
Including commented out flags that I've tried that also had no success
node_exporter log output
Are you running node_exporter in Docker?
What did you do that produced an error?
What did you expect to see?
What did you see instead?
It appears that node exporter does not ignore the filepaths correctly, because it maintains an OPENFILE on the pvc mount path. Output from a custom script written to determine this:
The text was updated successfully, but these errors were encountered: