123kateb Absent Member.
Absent Member.
1318 views

/dump filling up

Every few days each of the search appliances gets a large core dump file in /dumps. Any others have this issue and how to stop it from happening?
0 Likes
4 Replies
BSCHOOFS1 Absent Member.
Absent Member.

Re: /dump filling up


Can you be more specific on which dump folder is filling up?



However, in most cases, the issue is caused by the JVM running out of memory (mnot the system, but JVM memory).

This is addressed by increasing the JVM memory, but in order to do this safely, please also increase the assigned RAM, so the JVM is set to 3/4 of the assigned RAM.



If you have a large, expandable Filr infrastructure (with a /vashare) best practice woulsd be to set the assigned RAM to:

2GB for the OS + the size of JVM + size of Memcached + the size of the index*



* This is not always possible, but for an ideal world, and would allow the index node to load the index into memory during a index optimization. However a bare minimum of 2GB should be added,

To determine the index size use: du -h /vastorage/search/kablink/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: /dump filling up

Bart Schoofs:
> If you have a large, expandable Filr infrastructure (with a /vashare) best
> practice woulsd be to set the assigned RAM to:
> 2GB for the OS + the size of JVM + size of Memcached + the size of the index*


Most unfortunately this only works in very small environments as the
index can easily reach 100 GB or more which gets costly in RAM. JVM
clearly should give a warning in case of low memory instead of doing a
stupid dump and thus congesting the file system.

Günther

0 Likes
123kateb Absent Member.
Absent Member.

Re: /dumps filling up

It is the /dumps directory or mount point that fills up with the big core file. Usually it
stays at 1%

Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 20641404 5149016 14443864 27% /
udev 4097004 112 4096892 1% /dev
tmpfs 4097004 0 4097004 0% /dev/shm
/dev/sda1 20641404 5149016 14443864 27% /
/dev/sdb1 52014908 40903112 8490400 83% /var
/dev/sdc1 103211296 44727252 53241216 46% /vastorage
/dev/sdd1 51605116 184268 48799460 1% /dumps
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: /dump filling up

123kateb wrote:
>
> It is the /dumps directory or mount point that fills up with the big
> core file. Usually it
> stays at 1%
>
> Filesystem 1K-blocks Used Available Use% Mounted on
> rootfs 20641404 5149016 14443864 27% /
> udev 4097004 112 4096892 1% /dev
> tmpfs 4097004 0 4097004 0% /dev/shm
> /dev/sda1 20641404 5149016 14443864 27% /
> /dev/sdb1 52014908 40903112 8490400 83% /var
> /dev/sdc1 103211296 44727252 53241216 46% /vastorage
> /dev/sdd1 51605116 184268 48799460 1% /dumps
>
>


There is no /dumps directory or partition on Filr 2.0 indexing
appliances. Java dumps are written to
/var/opt/novell/search/indexserver/dumps
I created an extra partition for this in order to avoid filling up /var
with these files. As it has been mentioned already increasing the Java
Heap Memory might cure the issue.

Günther
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.