Why is the Memory Tracker not working as expected?

[dvg06]

Hi Splunkers,

We have set search_process_memory_usage_threshold to 3GB, but noticed that searches are terminated when the usage reaches much higher values, example below.
Is this expected behaviour, or is there any other parameter to be enabled make it work better?

09-13-2018 10:59:00.013 +1000 WARN  SearchProcessMemoryTracker - Dispatch Command: The search processs with sid=XXXX was forcefully terminated because its physical memory usage (5626.160000 MB) has exceeded the 'search_process_memory_usage_threshold' (3000.000000 MB) setting in limits.conf.

[dvg06]

Thanks traxxasbreaker

[traxxasbreaker · Accepted solution]

Most likely the search's memory passed the threshold very quickly in between memory tracker doing its periodic checks. At a glance of the available limits.conf settings, I don't see anything that would let you tune the polling interval of memory tracker.

[dvg06]

thanks @traxxasbreaker.

Do we get an option to configure this period for checks?