nspcc-dev / nspcc-dev/neofs-node
Continue serving GET from other node on failure
Open
Nobody has claimed this yet.
blocked
enhancement
I4
neofs-storage
S4
U3
- 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 GET can't continue serving data from other node if current one fails for whatever reason. This can happen when streaming data at any point.
Describe the solution you'd like
Skip the initial chunk and continue via other node.
Additional context
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 the behavior described in this issue and the related pull request #3833. Trace the GET streaming path and its node-failure handling, then determine how skipping the initial chunk and continuing from another node should work. Done means GET can continue serving data after a node fails during streaming, with tests covering the failure path.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100