Omiagent seems to leak memory with OmsAgent and Docker about omi HOT 5 CLOSED

More specifics about the setup. The nodes are setup using docker-machine as a five node swarm cluster, new 1.12 swarm mode. Five swarm nodes are thus created and they are all joined to the swarm as managers.

The swarm started as 1.12.1 but has later been upgraded to 1.12.3 without issues. Also, OmsAgent started as the previous version but was upgraded. Of notice is that it seems to have tried to update itself at some point and failed.

The latest version of the OmsAgent was then manually reinstalled in order to re-establish logging to OMS. Previously we had the situation with OmsAgent bits frequently crashing. This seems to have been resolved with this later version, however the new behaviour with memory growth started. I did not see such memory growth previously. I have no idea what version of omiagent the previous version of OmsAgent used.

from omi.

More weird behaviour. After deploying a new service to the swarm, the omiagent on that particular host the container was scheduled to suddenly stopped leaking memory. The others still do.

from omi.

This is actually a problem with the Docker Provider, I believe. It's running omiagent, but omiagent launches code from another project.

The Docker Provider is released with OMS. Please report bugs there, as they are responsible for the overall OMS project, and they know what new versions are in the works for bug fixes.

Please be certain you're running the latest/greatest version of OMS. If you are, please open an issue there to report that. Thanks.

I'm going to close this issue since it's not related to OMI directly. I think the memory growth issue is known too, but check the OMS issues for more information.

from omi.

I am observing the same problem in my Ubuntu 14.04.4 LTS hosts. I couldn't find any related issue in OMS. Do you know if the most recent OMS version solved the problem or if there is any work-around?

from omi.

@helderpinto Please see my prior response posted on February 6th.

OMI is not the issue here. OMI is just the transport, any provider can leak memory, and OMI has nothing to do with that.

Please open an issue with OMS, and they should be able to help you. Thanks.

from omi.