nspcc-dev / nspcc-dev/neofs-node
Lost object handling in meta
Open
Nobody has claimed this yet.
enhancement
I4
neofs-storage
S4
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Objects can be lost. Three machines going down with REP 3 is exactly that case. This fact should be reflected in the contract, signed by all current container machines. Then the object entry can be dropped from the metabase.
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
The issue names no files, tests, or entry points. Start by clarifying how REP 3 loss is represented in the contract and how the metabase entry is removed; done should mean the contract reflects the loss and the object entry can be safely dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100