When performing a real-time search, the search takes an exceptionally long time or you see the error:
An error occurred processing your request. Please try again.
You run the top command and see the Java process consuming high memory on the Active response server.
This process is responsible for elastics search and the
postgress process. If you view this output over time, you see Memory utilization % increases and isn't released.
For example: The Java process consumes 4.5 GB and
postgress consumes 13 GB of total memory. Over time, the memory use increases.
USER |
PR |
NI |
VIRT |
RES |
SHR |
S |
%CPU |
%MEM |
TIME+ |
COMMAND |
elastics |
20 |
0 |
3104m |
1.4g |
249m |
S |
124.3 |
4.5 |
07:12.2 |
java |
mfetie |
20 |
0 |
4404m |
4.1g |
4.1g |
S |
2 |
13 |
04:23.9 |
postgres |