Inodes as a scheduling parameter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
We are exhausting Inodes before we are exhausting disk space see attached image.
Since Inodes aren't known until run time putting in a threshold rule where no jobs will be scheduled on a node which has exhausted X% of Inodes would be good.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the scheduler's node-eligibility checks and existing resource threshold configuration. Determine how runtime inode exhaustion could be measured and exposed as a scheduling threshold, then verify that jobs are not placed on nodes exceeding it and that existing scheduling behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100