You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some context:
Used helm to install grafana + loki etc.
It does not matter in which node grafana ends up, it causes wormhole's memory to go up, it takes less than 24 hours to go up to 1.5GB and eventually will reach a limit and everything in that node starts having trouble
There was an issue in grafana which i solved, so the issue is now gone, but the wormhole pod continues to cause trouble.
I understand that grafana is causing this, but the memory in grafana is fine and performance on grafana is fine. However, wormhole imo should not do this no matter what
The text was updated successfully, but these errors were encountered:
Interesting. Can you share more details? Where are you running the wormhole? Is it the latest version? I remember a memory leak that was fixed a long time ago.
It could be that, and the kubernetes cluster that I have is just running an old version .. I am afraid i have no more information than that. In fact, after checking it again once I fixed more issues in grafana, the stopped happening. So the issue is solved, i just wanted to report here, hoping that it would help someone avoid this in the future!
Some context:
Used helm to install grafana + loki etc.
It does not matter in which node grafana ends up, it causes wormhole's memory to go up, it takes less than 24 hours to go up to 1.5GB and eventually will reach a limit and everything in that node starts having trouble
There was an issue in grafana which i solved, so the issue is now gone, but the wormhole pod continues to cause trouble.
I understand that grafana is causing this, but the memory in grafana is fine and performance on grafana is fine. However, wormhole imo should not do this no matter what
The text was updated successfully, but these errors were encountered: