nspcc-dev / nspcc-dev/neofs-node
Investigate and document all possible disk errors that shoud count in shard error counter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
As an example we have recently encountered too many open files error because of wrong system configuration.
Should we count them in the shard error counter?
Currently we count all errors from Open/Write as "physical" errors. Maybe we should behave differently in some situations.
Contributor guide
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
Inspect the shard error-counter handling for errors returned by Open and Write, starting with the existing classification of all such errors as physical. Identify the disk errors that should count, including the reported “too many open files” case, and document the final classification and rationale; done means the supported cases and intended counter behavior are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100