[Pacemaker] Release candidate: 1.1.10-rc3

[Andreas Mock]

Hi Andrew,

waiting for the RHEL 6.x build of pacemaker 1.1.10 I want to ask
whether there can be done something for finding the memory leaks.
If so, than explain the steps needed in detail. Currently there
are two real clusters available to do testing.

(Questions: Do you need logs? Debug-Log? Some excerpt? Shall we look
for certain patterns?)

Best regards
Andreas Mock


-----Ursprüngliche Nachricht-----
Von: Andrew Beekhof [mailto:andrew at beekhof.net] 
Gesendet: Mittwoch, 5. Juni 2013 04:26
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Release candidate: 1.1.10-rc3


On 23/05/2013, at 12:33 PM, Andrew Beekhof <andrew at beekhof.net> wrote:

> Please keep the bug reports coming in.  There is a good chances that
> this will be the final release candidate and 1.1.10 will be tagged on
> May 30th.

I am delaying rc4 until we can get definitive closure on the crmd memory
leak(s).
Valgrind has given it a clean bill of health, however the process still
appears to be growing over time and at strange intervals, so its not yet
clear what is responsible.

Beyond fixes for memory leaks, rc4 will include a workaround for
inconsistent tls handshake behavior between gnutls versions and some
improvements to the way crm_resource can be used to move resources around.
I hope to provide more detail soon.

-- Andrew
_______________________________________________
Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org