High memory usage on TAS Diego Database
search cancel

High memory usage on TAS Diego Database

book

Article ID: 454553

calendar_today

Updated On:

Products

VMware Tanzu Application Service

Issue/Introduction

After upgrading the TAS Tile to version 10.4.2, customer noticed that the Diego Database component started to increase memory usage.

Environment

TAS 10.4.2

Cause

There’s a connectivity issue between the foundation and the syslog server causing high memory usage.

Resolution

Use the Top command to check the top memory consumer.  

Top consumers:

 

rsyslogd: 247.6 MiB (25.3%)

bbs + bosh-dns: 132.9 MiB (13.6%)

syslog-agent, forwarder-agent, etc.: 42.5 MiB (4.4%) 

 

If rsyslogd is consuming a lot of memory, check the /var/log/syslog logs for errors. You might see something like this:

rsyslogd: cannot connect to #.#.#.#:514 (took 0.00 seconds): Connection refused [v8.2604.0 try https://www.rsyslog.com/e/2027]

 

If there’s a connectivity issue, the rsyslog process will have a local log backlog causing high memory usage in the top output. Check your network firewall or load balancer for any connectivity problems between the foundation and the external syslog server. 

Additional Information

 High CPUand Memory Usage on Gorouter and Diego Database VMs After Upgrade to EAR 10.4