nspcc-dev / nspcc-dev/neofs-node
IR stops processing (some?) requests after RPC reconnection
Open
Nobody has claimed this yet.
bug
I4
neofs-ir
S4
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Expected Behavior
RPC connection loss -> reconnect -> continue working with notary requests as usual.
Current Behavior
RPC connection loss -> reconnect -> node bootstrap requests are no longer processed.
Possible Solution
Fix something.
Steps to Reproduce (for bugs)
External RPC, drop connection. Most likely it's not 100% reproducible.
Context
This has happened on mainnet.
Regression
Doesn't look like.
Your Environment
- Version used: 0.49.0
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 tracing external RPC reconnection and the handling of node bootstrap requests in the Go code. Reproduce the issue by dropping the RPC connection and observing behavior after reconnection; done means node bootstrap and notary requests continue processing normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100