corosync 3.0.2-pve4 memory leak

grin

Renowned Member
Dec 8, 2008
172
21
83
Hungary
grin.hu
I have a (possibly unrelated) problem where one cluster member's TOTEM keep generateing retransmits from other nodes or local timeouts. When I checked nodeC kept joining and leaving the cluster, about 50 per seconds. Restarting corosync resulted the same.

It turned out however that on other nodes corosync memory consumption at that point was 18 gigabytes, out of that 18 gigabytes residential. This is clearly suboptimal in itself, however it turned out that until I have restarted all of them on all nodes nodeC corosync cannot be started without generating thousands of join/leave events per minute (and more memory to be eaten on the others).

Restaring all gave me 600M (normal) memory consumption and nodeC able to join without errors.
 
Code:
557b49a8b000-557fb2d9a000 rw-p 00000000 00:00 0                          [heap]
Size:           18500668 kB
KernelPageSize:        4 kB
MMUPageSize:           4 kB
Rss:            18500668 kB
Pss:            18500668 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:  18500668 kB
Referenced:     18500668 kB
Anonymous:      18500668 kB
LazyFree:              0 kB
AnonHugePages:         0 kB
ShmemPmdMapped:        0 kB
Shared_Hugetlb:        0 kB
Private_Hugetlb:       0 kB
Swap:                  0 kB
SwapPss:               0 kB
Locked:         18500668 kB
THPeligible:    0
VmFlags: rd wr mr mw me lo ac sd
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!