-
Notifications
You must be signed in to change notification settings - Fork 43
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
vip-manager RAM usage steadily increases till OOM killed by system #285
Comments
Hello, Excuse me, I don't know, if I can write them in this thread or I should open a new one. We have the same problem in all servers, when we use vip-manager with Patroni datasource. Operating system: vip-manager version: 2.8.0 Config. file: vip-manager-dbasync.yml Running vip-manager processes:
vip-manager.yml uses etcd datasource The process's data: sudo pmap -X 2037 When we restarted the process, the inital memory usage: Thank you for the help! |
would you please check the #286 if it fixes the issue? Thanks in advance! |
@pashagolub thank you very much for the quick update! We installed the fix on the server and are monitoring the RAM too see if the usage remains stable. I'll post the results tomorrow. |
@pashagolub it seems to be fine now. Memory usage has remained stable since the update. Is this fix going to be added to the 2.8 version, or will it be released in 2.9? Thanks again for the great help! |
Thanks a lot! This will be a new release. I'm working on it right now! |
We also tested this update, it works well. |
I Have recently upgraded vip-manager 2.3.0 from the ubuntu repos to the newest vip-manager version 2.8.0 from this github repo. The issue began after installing the newest version.
I wanted to have the newest version so I can use patroni as the vip-manager endpoint. This ensures that vip-manager still functions when patroni is in failsafe_mode and/or etcd is unreachable.
OS: Ubuntu 24.04 LTS
vip-manager: version: 2.8.0, commit: 8aef662
patroni: 3.2.2
Screenshot of the system RAM usage:
Logs when vip-manager gets OOM killed:
These are the logs from the standby server so the state is false, desired false from vip-manager is correct. The issue also occurs on the leader server.
Enabling debug and verbose options does not give additional logs.
My vip-manager Config:
My Patroni API Config:
I am starting the vip-manager via systemD. The Unit file looks like this:
I have overridden the ExecStart so I can use a custom File. This because if the package from the ubuntu repos ever gets installed again it wont override the custom parameters in the unit file.
The overall behavior of vip-manager is correct and works without issues in failover situations. The only problem is that vip-manager fills up the system RAM gets killed and repeats this. This creates a downtime for the whole server every 2 days.(depending on how much RAM you have)
The text was updated successfully, but these errors were encountered: