-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hornet 2.0.1 -- Kubernetes -- oommkilled #1931
Comments
How much TPS do you produce? And why is that a bug? |
The spammer just connect and memory consumption starts to increase. It didn't send any message. Yes! It's not necessary a bug in hornet! I presupposed as bug because in the docker is working very well. Sorry! :-) If you want more evidence, I'll be happy to help. I have been using Hornet 1.2 on Kubernetes for a long time and it works great in my environment. |
I made a short film showing the behavior! ScreenRecorderProject1_2.mp4 |
Hi @muXxer I found the problem, I entered the wrong address in the indexer. I corrected my script, but in your opinion, is this a possible problem in the Hornet? Thanks! |
Hi,
I am migrating the one-click-tangle to hornet 2.0.1, the migration was very well, but the hornet 2.0.1 is unstable in the kubernetes.
I needed to increase the memory of my nodes, but the problem is occuring yet.
The nodes had 16Gi each and now 32Gi each.
I needed to set vm.overcommit_ratio=90 and the hornet establed for a while, but after the comsumption of memory was unstable until I get OOM again.
Event error:
"Memory cgroup out of memory: Killed process 180904 (hornet) total-vm:12642108kB, anon-rss:9701844kB, file-rss:43452kB, shmem-rss:0kB, UID:65532 pgtables:19416kB oom_score_adj:984"
P.S.: The problem happens after the spammer connects to Hornet 2.0.1
Expected behavior
Hornet 2.0.1 stable memory consumption.
Environment information:
Additional context
Hornet Deployment
Config.json
Spammer
Config Spammer
The text was updated successfully, but these errors were encountered: