Re: Release Notes for v210
|
Eric Malm <emalm@...>
Hi, all,
toggle quoted messageShow quoted text
Please be aware that the Diego team has recently identified a goroutine and memory leak in the Diego codebase for release 0.1247.0 that eventually affects the performance of Diego's receptor component. Further investigation has revealed that this leak was introduced in final release 0.1221.0 and fixed in 0.1259.0. Consequently, we do not recommend the use of Diego final releases from 0.1221.0 through 0.1258.0 in long-running environments. If you do need to mitigate this issue in such an environment, issuing a 'monit restart' to each receptor process on the Diego 'access' VMs once it consumes a majority of available memory on the VM should suffice and should have negligible impact on the performance and availability of the Diego backend, especially if more than one 'access' VM is present in the Diego deployment. The next final release of CF (namely, v211) will be accompanied by a Diego final release that does not exhibit this problem. Additionally, the Diego team has identified and corrected the gaps in our testing pipeline and monitoring configuration that allowed this resource leak to slip through. Thank you for your understanding, and please let me know if you have further questions about this matter. Best, Eric, CF Runtime Diego PM
On Tue, May 26, 2015 at 10:59 PM, Dieu Cao <dcao(a)pivotal.io> wrote:
The cf-release v210 was released on May 23rd, 2015
|
|
|