pmxcfs use 45% memory

[lyddragon]

pmxcfs takes up too much memory, to 45%.
Can I restart the process?
run command: systemctl restart pve-cluster.service ?

 

[dcsapak]

yes you should be able to restart pve-cluster,

what is your pveversion -v ?

 

[Rhinox]

As I see, you still have ~3.3GB of free memory. So why should you do that???

Honestly I do not understand this obsession. You have memory, so let OS using it! Every modern OS folows one simple rule: any using of memory is better than not using it at all. If you are trying to keep as much free memory as possible, you are going against that rule. Then you have to write your own memory-manager...

 

[lyddragon]

Version: Virtual Environment 4.4-1/eb2d6f1e

CPU:
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 40
On-line CPU(s) list: 0-39
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz

Memory:
$ free -g
total used free shared buffers cached
Mem: 125 125 0 1 0 1
-/+ buffers/cache: 123 2
Swap: 7 5 2

 

[lyddragon]

• Will it affect running virtual machines? if run command "systemctl restart pve-cluster.service "

 

[lyddragon]

$ pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

 

[kotelgg]

OS folows one simple rule: any using of memory is better than not using it at all.

But if the system wants run backup, then fail, becouse it needs memory.

 

[esi_y]

Was this memory leak eventually identified?