# CPU/Memory consumption after upgrading to Version 5.1.2 **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [January 25, 2017, 7:03am UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735 "2017-01-25T07:03:16Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![tokraft](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tokraft/32/14888_2.png) [@tokraft](https://discuss.elastic.co/u/tokraft)\ **Post date:** [January 25, 2017, 7:03am UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/1 "2017-01-25T07:03:16Z")
Hi, last week I upgraded metricbeat from version 5.1.1 to version 5.1.2. When I take a look at the memory and also the CPU consumption of metricbeat itself for the last 7 days it seems that metricbeat is continuously consuming more memory and CPU. After restarting the metricbeat process it seems working fine again, but memory and CPU load starts increasing again (see also attached screenshot). Are there any known issues or hints? We are running metricbeat on Ubuntu Linux 16.04 and have activated the standard metrics and also monitoring for docker containers. Many thanks, Tobias ![](https://us1.discourse-cdn.com/elastic/original/2X/a/af1ddfbd92b68bbd078820e3b05352c877b41d02.png) ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [January 25, 2017, 1:46pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/2 "2017-01-25T13:46:41Z")
Reminds me of [https://github.com/Ingensi/dockbeat/issues/139](https://github.com/Ingensi/dockbeat/issues/139) Is there any chance that you could check if the memory issue also happens without the docker module? ---
**Author:** ![tokraft](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tokraft/32/14888_2.png) [@tokraft](https://discuss.elastic.co/u/tokraft)\ **Post date:** [January 25, 2017, 2:38pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/3 "2017-01-25T14:38:30Z")
Hi Nicolas, I have now disabled docker and will provide feedback in a few days on the memory and the CPU usage. ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [January 26, 2017, 12:00pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/4 "2017-01-26T12:00:24Z")
Thanks for testing this. Let me know as soon as you have some indications here. How many containers are you monitoring? In case it is docker, my first assumption is that we leak some http handlers or something similar. ---
**Author:** ![tokraft](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tokraft/32/14888_2.png) [@tokraft](https://discuss.elastic.co/u/tokraft)\ **Post date:** [January 26, 2017, 1:45pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/5 "2017-01-26T13:45:02Z")
Hi Nicolas, we are monitoring currently only 6 Containers. The monitoring period was set to 20s. ---
**Author:** ![tokraft](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tokraft/32/14888_2.png) [@tokraft](https://discuss.elastic.co/u/tokraft)\ **Post date:** [January 28, 2017, 12:07pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/6 "2017-01-28T12:07:19Z")
Hi Nicolas, we are now monitoring our server for three days without the docker metrics and it seems that metricbeat is running fine. Memory and CPU is not increasing. As a workaround I will now activate the docker metrics again and restart metricbeat every hour by adding a crontab entry. ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [January 30, 2017, 7:28am UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/7 "2017-01-30T07:28:27Z")
Ok, that sounds like there is some memory leak in the docker module. Could you open a Github issue for that? [https://github.com/elastic/beats](https://github.com/elastic/beats) ---
**Author:** ![tokraft](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tokraft/32/14888_2.png) [@tokraft](https://discuss.elastic.co/u/tokraft)\ **Post date:** [January 30, 2017, 7:48am UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/8 "2017-01-30T07:48:57Z")
Here is the Github issue: [https://github.com/elastic/beats/issues/3489](https://github.com/elastic/beats/issues/3489) ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [January 31, 2017, 12:04pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/9 "2017-01-31T12:04:09Z")
Thanks. Lets continue the conversation there. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 28, 2017, 12:04pm UTC](https://discuss.elastic.co/t/cpu-memory-consumption-after-upgrading-to-version-5-1-2/72735/10 "2017-02-28T12:04:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.