pingcap / tiup

A component manager for TiDB

Home Page:https://tiup.io

Repository from Github https://github.compingcap/tiupRepository from Github https://github.compingcap/tiup

Add check for inode numbers in `tiup cluster check`

JaySon-Huang opened this issue · comments

commented

Feature Request

Is your feature request related to a problem? Please describe:

Before v7.4, TiFlash may happens to inode exhausting and cause panic. Especially when users deploy TiFlash on a file system with a particularly small number of inode nodes.

pingcap/tiflash#7595

Describe the feature you'd like:

Normally, the bytes-per-inode is 1024KiB, so we can get the expected inode number according to the total disk size. TiUP can check if the actual inode number is in the same order of magnitude as expected. If the number of inodes is too small, give a warning to the user.

Why the featue is needed:

Before v7.4, TiFlash could suffer from inode exhaust when

  • Users create ten thousands of empty partition tables
  • Users load lots of data of a wide table with many columns to TiFlash

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy: