High CPU Utilization seen in NSX manager in proton/java
search cancel

High CPU Utilization seen in NSX manager in proton/java

book

Article ID: 411879

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Slow web UI and CLI access of the NSX Manager is noticed
  • API execution for NSX Manager will be slow 
  • New configuration would take time to get applied
  • We see the Java Command utilizing high amount of CPU using the top command
    top output of the NSX Manager :
      PID  USER    PR NI VIRT    RES    SHR  S %CPU %MEM  TIME+   COMMAND
     6889 uproton 20 0 8405540 4.990g 16184 R 99.9 31.8 26841:44 java
  • /var/log/proton/proton-tomcat-wrapper.log
    search for nid=0x1ae9 (0x1ae9 is retrieved by converting 6889 to hex)
    INFO   | jvm 1    | 2018/08/16 15:54:07 | "Concurrent Mark-Sweep GC Thread" os_prio=0 tid=0x00006f8b08067000 nid=0x1ae9 runnable
  • Check the /var/log/proton/gc.log* (Check if the count is More)
    grep "Full GC" gc.* | wc -l


Environment

VMware NSX-T Data Center
VMware NSX

Cause

This issue is caused by memory leak in the proton service.

Resolution

Restart NSX Manager to temporarily resolve the issue.