The server with the actual problem is st02 (192.168.0.213) but all the other nodes are also going up with the ram usage

# gluster volume info

Volume Name: static
Type: Replicate
Volume ID: 3aede3c2-6076-41f6-b0f6-25209faf7906
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 192.168.0.211:/mnt/brick0/static
Brick2: 192.168.0.213:/mnt/brick0/static
Options Reconfigured:
performance.cache-size: 4096MB
nfs.addr-namelookup: off
nfs.export-volumes: on
auth.allow: 192.168.0.*
nfs.rpc-auth-allow: 192.168.0.*
performance.readdir-ahead: on

Volume Name: webroot
Type: Replicate
Volume ID: 728d0c17-3bab-45be-93d7-a6fc2fb963d2
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.0.205:/mnt/brick0/webroot
Brick2: 192.168.0.207:/mnt/brick0/webroot
Brick3: 192.168.0.209:/mnt/brick0/webroot
Options Reconfigured:
performance.readdir-ahead: on
auth.allow: 192.168.0.*
nfs.rpc-auth-allow: 192.168.0.*
nfs.export-volumes: on
nfs.addr-namelookup: off
performance.cache-size: 4096MB

all the 5 servers and additionally 2 cron servers are mounting webroot and static
