[Pacemaker] Corosync memory usage rising

[Yves Trudeau]

Hi,
    Is there any known memory leak issue corosync 1.4.1.  I have a setup 
here where corosync eats memory at a few kB a minute:

[root at mys002 mysql]# while [ 1 ]; do ps faxu | grep corosync | grep -v 
grep; sleep 60; done
root     11071  0.2  0.0 624256  8840 ?        Ssl  09:14   0:02 corosync
root     11071  0.2  0.0 624344  9144 ?        Ssl  09:14   0:02 corosync
root     11071  0.2  0.0 624344  9424 ?        Ssl  09:14   0:02 corosync

It goes on like that until no more memory which is still a long time. 
Another has corosync running for a long time:

[root at mys001 mysql]# ps faxu | grep corosync | grep -v grep
root     15735  0.2 21.5 4038664 3429592 ?     Ssl   2012 184:19 corosync

which is nearly 3.4GB.

[root at mys002 mysql]# rpm -qa | grep -i coro
corosynclib-1.4.1-7.el6_3.1.x86_64
corosync-1.4.1-7.el6_3.1.x86_64
[root at mys002 mysql]# uname -a
Linux mys002 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 
x86_64 x86_64 x86_64 GNU/Linux

looking at smaps of the process, I found this:

020b6000-d2b34000 rw-p 00000000 00:00 0
Size:            3418616 kB
Rss:             3417756 kB
Pss:             3417756 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:   3417756 kB
Referenced:      3417064 kB
Anonymous:       3417756 kB
AnonHugePages:   3416064 kB
Swap:                  0 kB
KernelPageSize:        4 kB
MMUPageSize:           4 kB


this setup is using udpu

totem {
         version: 2
         secauth: on
         threads: 0

          window_size: 5
          max_messages: 5
          netmtu: 1000

          token: 5000
          join: 1000
          consensus: 5000

         interface {
                  member {
                         memberaddr: 10.103.7.91
                 }
                 member {
                         memberaddr: 10.103.7.92
                 }
                 ringnumber: 0
                 bindnetaddr: 10.103.7.91
                 mcastport: 5405
                 ttl: 1
         }
          transport: udpu
}

with special timings because of issues with the vmware setup.

Any idea of what could be causing this?

Regards,

Yves