-
Notifications
You must be signed in to change notification settings - Fork 16
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
possible memory leak #136
Comments
Are you using the jvm or native distribution? |
Native .. phoenix-0.4.2-linux-x64.zip |
Do you have other software running on that VM? What kind of usage (api calls, payments) are you doing with phoenixd? Are you actively sending/receiving payments or is it pretty much idle? |
It's running by itself in a docker container. Most of the time it's idle and only gets calls when the admin console is active or people are using their bolt card. The rest of the VM is also very light use. The VM is low resource (and low cost) from lunanode. It is part of the Bolt Card Hub - Phoenix Edition project which is an open source back end to provide services for a set of bolt cards and uses this Phoenix DockerFile to provision phoenixd. |
I am managing some phoenixd instances running on VMs with modest resources (1 Gb RAM) over a long period of time.
These seem to consistently run out of memory after ~80 days with the phoenixd service being identified as having a large memory allocation and being killed by linux after an out-of-memory event.
The text was updated successfully, but these errors were encountered: