mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Replicator repeatedly can't get data from RPC #1474
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1474
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roman-khimov on GitHub (Aug 7, 2025).
Expected Behavior
Reconnect of some kind solving the problem.
Current Behavior
Possible Solution
Reconnect, continue operation.
Steps to Reproduce (for bugs)
Unknown. It just happened.
Context
But it happened on mainnet.
Regression
Unknown.
Your Environment
@roman-khimov commented on GitHub (Aug 7, 2025):
For whatever reason all four nodes were stuck this way.
@roman-khimov commented on GitHub (Aug 7, 2025):
@roman-khimov commented on GitHub (Aug 7, 2025):
It reproduced on m3, but restored eventually.
@roman-khimov commented on GitHub (Aug 7, 2025):
But before reconnect it's
@roman-khimov commented on GitHub (Aug 7, 2025):
So it fails requests, but receives an event. Pretty strange combination.
@roman-khimov commented on GitHub (Aug 7, 2025):
It's as if writer thread is done in WSClient, but reader is still active. Which shouldn't happen, broken connection is broken for both sides. We also have some ping-ponging.
@roman-khimov commented on GitHub (Aug 7, 2025):
Another case:
@roman-khimov commented on GitHub (Aug 7, 2025):
Looks like we can't process an event here.
@roman-khimov commented on GitHub (Aug 7, 2025):
And it's GC blocking things because previous iteration hasn't finished yet.