nspcc-dev / nspcc-dev/neofs-node
Split context in EC GET
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
You don't have many options with EC, nodes need to cooperate to produce the result. The only option maybe is splitting the context, try optimistic scenario for half of time then fallback to fetching parity if we can't get enough regular parts in time.
Originally posted by @roman-khimov in https://github.com/nspcc-dev/neofs-node/pull/3497#discussion_r2324507392
Additional context
#3240
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 discussion referenced in the issue and the additional context in #3240 to understand the EC GET constraints and proposed context split. Trace the existing EC GET flow and identify how optimistic regular-part fetching and parity fallback are coordinated; done means a reviewed design and implementation that handles both paths correctly.
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