-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Labels
I4No visible changesNo visible changesS4RoutineRoutineU0Needs to be resolved immediatelyNeeds to be resolved immediatelybugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issues
Milestone
Description
Expected Behavior
No errors.
Current Behavior
warn neofs-node/container.go:247 put report to contract error {"component": "containerReports", "epoch": 5, "cid": "7NPVTC9bBcthSJsSx6dQi1iKjWv9iWtgQoGULeMP6FzV", "error": "could not invoke method (putReport): failed to submit notary request: waiting for the response: connection lost: failed to write ping message: write tcp [::1]:60876->[::1]:30333: write: broken pipe"}
error neofs-node/object.go:70 could not get max object size value {"error": "(*netmap.Client) could not get epoch number: could not perform test invocation (config): waiting for the response: connection lost: failed to write ping message: write tcp [::1]:60876->[::1]:30333: write: broken pipe"}
warn neofs-node/container.go:236 unable to fetch container data {"component": "containerReports", "epoch": 5, "cid": "7Nn5Xze9Rakyep6XC5LDeGLTbyanTPYzT8i7UJ4VqKJF", "error": "could not perform test invocation (getContainerData): waiting for the response: connection lost: failed to write ping message: write tcp [::1]:60876->[::1]:30333: write: broken pipe"}
Possible Solution
Fix the damn thing.
Steps to Reproduce (for bugs)
Lots of containers, lots of objects coming in.
Context
Some performance test.
Regression
Looks like.
Your Environment
- Version used: 0.50.1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU0Needs to be resolved immediatelyNeeds to be resolved immediatelybugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issues