nspcc-dev / nspcc-dev/neofs-node
Fetching strategy if object is not found locally
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 know that a node responds with the first API (error) status it gets from another node even if there is more nodes to try.
Describe the solution you'd like
Try to get some meaningful number of the same responses and only then answers with it (REP number? 2/3+1 number?).
Describe alternatives you've considered
Complex statuses and the other things from the https://github.com/nspcc-dev/neofs-node/issues/1709#issuecomment-2044490058.
Additional context
https://github.com/nspcc-dev/neofs-node/issues/1709, https://github.com/nspcc-dev/neofs-node/pull/2836 (PR that makes local response priority).
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 reading issue #1709 and its linked discussion, then review pull request #2836 for the current local-response priority behavior. Clarify the required response threshold and how competing node responses should be handled; done means the fetching strategy uses the agreed meaningful-response rule rather than immediately returning the first error.
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