Show top process by mem list API actually responses top process by cpu list.

Products

• VMware NSX

Issue/Introduction

• Using following NSX API
  • GET api/v1/systemhealth/appliances/<uuid>/process/status
• processes in top_process_by_mem_list are not sorted by memory but cpu and identical to top_process_by_cpu_list

For example, top_process_by_mem_list equals to top_process_by_cpu_list.

    "top_process_by_mem_list": [
                  {
                    "process_id": "3670",
                    "user": "root",
                    "priority": "10",
                    "nice_value": "-10",
                    "virtual_memory_size": 5.107648,
                    "resident_memory_size": 0.916868,
                    "cpu_usage": 71.5,
                    "memory_usage": 3.7,
                    "command": "java",
                  },
                  {
                    "process_id": "5898",
                    "user": "corfu",
                    "priority": "10",
                    "nice_value": "-10",
                    "virtual_memory_size": 7.027164,
                    "resident_memory_size": 2.383,
                    "shared_memory_size": 19.748,
                    "cpu_usage": 42.7,
                    "memory_usage": 10.1,
                    "command": "java",

                  },
                  {
                    "process_id": "18355",
                    "user": "root",
                    "priority": "20",
                    "nice_value": "0",
                    "virtual_memory_size": 8.388236,
                    "resident_memory_size": 3.638,
                    "shared_memory_size": 1.684,
                    "cpu_usage": 31,
                    "memory_usage": 15.5,
                    "command": "java",

                  }
    ],
...
   "top_process_by_cpu_list": [
                  {
                    "process_id": "3670",
                    "user": "root",
                    "priority": "10",
                    "nice_value": "-10",
                    "virtual_memory_size": 5.107648,
                    "resident_memory_size": 0.916868,
                    "shared_memory_size": 0.033636,
                    "cpu_usage": 71.5,
                    "memory_usage": 3.7,
                    "command": "java",
                  },
                  {
                    "process_id": "5898",
                    "user": "corfu",
                    "priority": "10",
                    "nice_value": "-10",
                    "virtual_memory_size": 7.027164,
                    "resident_memory_size": 2.383,
                    "shared_memory_size": 0.019748,
                    "cpu_usage": 42.7",
                    "memory_usage": 10.1,
                    "command": "java",

                  },
                  {
                    "process_id": "18355",
                    "user": "root",
                    "priority": "20",
                    "nice_value": "0",
                    "virtual_memory_size": 8.388236,
                    "resident_memory_size": 3.638,
                    "shared_memory_size": 1.684,
                    "cpu_usage": 31,
                    "memory_usage": 15.5,
                    "command": "java",
                  }
    ]

Environment

NSX-T Data Center 3.x

NSX 4.x

Resolution

This issue is resolved in VMware NSX 4.2.2, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

As workaround, check top-mem.log