nspcc-dev / nspcc-dev/neofs-node
Network-wide default tombstone lifetime
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I look at #2246, it's a quick kludge, but not a proper fix.
Describe the solution you'd like
Long-term this better be a network-wide configuration option. Even though anyone can technically use any value all of the network should be aware of the appropriate one.
Really(really)-longer-term tombstones can be replaced with a better solution.
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
Start by reviewing issue #2246 to understand the current tombstone lifetime workaround and how it is configured. Determine the design and integration points for a network-wide default, with completion defined as a documented, agreed configuration that is consistently recognized across the network.
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
- 20/100