pingcap / pingcap/tiup

The Filesystem Inodes usage shown in NodeExporter is not correct

Open
#2,389 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/bug
Dominant language
Go
Stars
466
Forks
338
Avg merge
3d 7h
Merged PRs (30d)
8

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

Actually, it is an issue about NodeExporter, open an issue here because I don't know where it should be reported to.

  1. What did you expect to see?

  2. What did you see instead?

image
image

  1. What version of TiUP are you using (tiup --version)?

The deployed tidb cluster version is v7.5.1

tiup version is

>  tiup --version
1.14.0 tiup
Go Version: go1.21.5
Git Ref: v1.14.1
GitHash: 23f7b0f0f3a0ad29e90a7b12b1097e8d4074cb3e

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, reproduction steps, expected result, or TiUP entry point is identified. First verify whether the inode metric is produced by TiUP or NodeExporter, then locate the responsible component and establish a reproducible comparison. Done requires a confirmed owner, clear expected behavior, and a targeted fix or handoff.

Written by the indexing model from the issue text.

Assessment

Domain
observability
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.