nspcc-dev / nspcc-dev/neofs-node
Parallel shard init
Open
Nobody has claimed this yet.
enhancement
I4
neofs-storage
S3
U4
- 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 shards take a lot of time to initialize.
Describe the solution you'd like
Initialize them concurrently. Have fun with error handling.
Describe alternatives you've considered
Keep things as is. More robust, but slow.
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 locating the shard initialization entry point and tracing how initialization errors are currently handled. Compare the current sequential behavior with the desired concurrent behavior, including failure cases. Done means shards initialize concurrently without losing clear error reporting, with tests covering the new behavior.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100