SB-5 2016-04-29 Bonding memory leaks

Service bulletin: SB-5 Date: April 29, 2016

A memory leak bug has been found in two services that run on bonders and aggregators. The issues are as follow:

  1. The collectd service, which reports performance data to the management server, begins to use increasing amounts of memory on an aggregator when a bond is removed from the aggregator. This can occur due to a manual move, an automated move due to aggregator failover, or if a bond is deleted. Aggregators running Bonding 2014.4 or later are affected by this issue. Because running out of memory on an aggregator affects service availability for potentially numerous bonds, this is considered a serious issue.

  2. The salt-minion service, part of the SaltStack configuration management system, slowly takes increasing amounts of memory on both bonders and aggregators. This affects hosts running Bonding 2015.4. The rate of the memory leak is approximately 100 MB/week. Hosts with less than 1 GB of memory are most susceptible.

These issues were fixed in, or prior to, the 2015.4-26 patch.

All partners are advised to upgrade aggregators to the latest version of 2015.4 as soon as possible, and to upgrade bonders already on 2015.4 to the latest patch as soon as possible. If you are not comfortable performing the aggregator upgrades yourself, please contact Technical support and we will perform the upgrade for you.