-
Notifications
You must be signed in to change notification settings - Fork 49
Replication spike leads to OOM #3918
Copy link
Copy link
Open
Labels
I4No visible changesNo visible changesS4RoutineRoutineU4Nothing urgentNothing urgentbugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU4Nothing urgentNothing urgentbugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second
Expected Behavior
No OOM.
Current Behavior
OOM.
Possible Solution
Optimize memory consumption, throw away requests that can't be processed in time.
Steps to Reproduce (for bugs)
Not really known, but we need a lot of replications (or large objects?) to the same node with limited RAM (like 4G).
Context
Testnet.
Regression
No.
Your Environment
uname -a):