High CPU issue - logstash - java

We have installed perfsonar-toolkit in an Ubuntu 20 (vmware image) and we have persistent high CPU issues due to java process (user logstash) even when no perfsonar test are running.

We have reproduced the issue in 2 different Ubuntu 20, rebooting of the system doesn't fix the issue, as soon as the vm is up CPU keeps high.

top - 09:18:02 up 13 min, 4 users, load average: 4.03, 4.21, 2.58
Tasks: 384 total, 4 running, 380 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.4 us, 3.6 sy, 81.3 ni, 14.5 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
MiB Mem : 15989.6 total, 9402.4 free, 3357.5 used, 3229.7 buff/cache
MiB Swap: 4096.0 total, 4096.0 free, 0.0 used. 12252.7 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                    

28378 logstash 39 19 3794064 594852 21240 S 311.3 3.6 0:31.22 java
28072 root 39 19 1620984 1.4g 9036 R 26.8 8.9 0:26.37 clamscan
26594 root 20 0 9652 4008 3212 S 0.7 0.0 0:00.45 top
3089 root 20 0 766376 46840 32648 S 0.3 0.3 0:12.45 rte-sensor
3802 tejeiroc 20 0 4854504 326112 123440 S 0.3 2.0 0:09.60 gnome-shell
4050 tejeiroc 20 0 216324 41808 29936 S 0.3 0.3 0:01.33 vmtoolsd
5620 root 20 0 0 0 0 R 0.3 0.0 0:00.66 kworker/u8:0-events_power_efficient
26397 root 20 0 108068 14372 10932 S 0.3 0.1 0:00.33 nessus-agent-mo
28372 root 20 0 9656 3972 3168 R 0.3 0.0 0:00.05 top
1 root 20 0 169996 13548 8520 S 0.0 0.1 0:16.37 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 slub_flushwq
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-events_highpri

Is there any known issue related to this?
Any information would be very much appreciated.

No repository file, test, or entry point is identified. Begin by reproducing the persistent Java process load on the Ubuntu 20 VMware image and inspect the logstash service alongside the supplied top output. Done means identifying the cause of the idle CPU usage and documenting a verified fix or clear diagnostic conclusion.