what is elastic+ management plane cpu process?

[Ankit1Singh]

Can anyone explain why elastic+ is showing in show system resources command?

17162 elastic+  20   0 3923.0g  38.0g   3.3g S   5.9 15.1 168339:53 java

18242 elastic+  20   0 3921.6g  38.0g   3.3g S   5.9 15.1 163177:55 java

top - 19:19:39 up 104 days,  1:59,  1 user,  load average: 3.61, 4.93, 5.40

Tasks: 662 total,   1 running, 370 sleeping,   0 stopped,   4 zombie

%Cpu(s):  4.1 us,  1.1 sy,  0.0 ni, 92.2 id,  2.3 wa,  0.1 hi,  0.1 si,  0.0 st

KiB Mem : 26297164+total,  5011872 free, 15112670+used, 10683307+buff/cache

KiB Swap:     7996 total,        0 free,     7996 used. 10938467+avail Mem

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

43844       20   0 2153664 889024  37032 S  94.1  0.3  17029:06 logd

13635       20   0 7262472   2.8g 105520 S  70.6  1.1  38176:14 pan_vld

13070       20   0 7226412   2.8g 107988 S  41.2  1.1  38968:52 pan_vld

43222       20   0  998576 132996  18948 S  17.6  0.1  10866:33 mgmtsrvr

7963       20   0   44984   6148   3832 R   5.9  0.0   0:00.02 top

12546       20   0 2192092  89300  39868 S   5.9  0.0 451:55.12 mongod

17162 elastic+  20   0 3923.0g  38.0g   3.3g S   5.9 15.1 168339:53 java

18242 elastic+  20   0 3921.6g  38.0g   3.3g S   5.9 15.1 163177:55 java

    1       20   0    4388   1260   1156 S   0.0  0.0   1:39.69 init

[F.Pinar]

Hi team,

I am getting the same issue with a PANORAMA 11.1.2-H3 

2024-09-04 06:18:32.585 -0600  --- top
top - 06:18:32 up 69 days, 16:27,  0 users,  load average: 29.11, 28.40, 27.02
Tasks: 383 total,   1 running, 380 sleeping,   0 stopped,   2 zombie
%Cpu(s): 68.1 us, 12.5 sy,  0.1 ni, 14.6 id,  0.0 wa,  1.0 hi,  3.7 si,  0.0 st
MiB Mem :  64411.9 total,    792.8 free,  47941.2 used,  15677.9 buff/cache
MiB Swap:   2047.9 total,   1191.2 free,    856.8 used.  18956.9 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
9597 elastic+  20   0   76.0g  32.9g 957900 S 987.9  52.2  24322:50 java

Is this issue related to Pan-223488 even though they are different models ?

PAN-223488

On the M-600 appliance, closed ElasticSearch shards are not deleted from the M-600 appliance. This causes the ElasticSearch shard purging to not work as expected, resulting in high disk usage.