This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forย 
Search instead forย 
Did you mean:ย 

Snaplex Node Freezing with High Memory

nsmith
New Contributor III

โ€Ž01-02-2018 08:20 AM

One of our SL Nodes freezes on high memory and wonโ€™t start any new pipelines or accept any webhooks. The only way weโ€™ve found to fix this is a manual reboot.

Memory will be going between 70-85%, and CPU between 10-60%โ€ฆ everything will be working fineโ€ฆ then suddenly the memory % stops changing, and CPU falls to 2-3%. It stays in this stage until we manually reboot. We arenโ€™t receiving any alerts for this either.

Is anyone having the same problem? Any ideas on how to fix this issue?

It would be great if SL would catch this issue and automatically restart the node.

0 Kudos
8 REPLIES 8

jaybodra
New Contributor III

โ€Ž01-04-2018 02:19 PM

Had similar issue and the node use to restart cause it would crash (Ran out of memory). I have a ticket for this issue.

I would be glad if snaplogic is able to free up memory on its own. (Tried to do it with jython script which didnt work either)

0 Kudos

wani-amol
New Contributor III

โ€Ž07-08-2019 10:30 AM

Any idea if this issue was resolved and SnapLogic applied a patch for this?Hitting the same issue.

0 Kudos

akidave
Employee
Employee

โ€Ž07-08-2019 05:58 PM

Most issues causing high memory usage are Snaplex capacity issues. The pipeline workload would have to analyzed and tuned to find why memory usage is high. Things which help to avoid memory issues include

  1. Reduce concurrency in PipeExec snap
  2. Reduce max memory usage setting in Sort and In-Memory Lookup snaps
  3. Add additional nodes in the Snaplex (horizontal scaling). This is useful if the workload is parallelizable at the pipeline level. Setting the Snaplex property in the PipeExec snap will ensure that the pipeline workload gets distributed across nodes in the Snaplex.
  4. Increase heap memory available on the Snaplex nodes (vertical scaling). This can be used when the workload is not easily parallelizable at the pipeline level.

If the issue is that memory usage does not go down after pipeline execution completes, that would be unusual. Look at any custom snaps and scripts being used to see if they could be causing leaks. If the issue still persists, open a Support ticket for further investigation.

0 Kudos

aditya_kurhade
New Contributor
In response to akidave

โ€Ž10-05-2019 05:42 AM

hi @akidave,
we have written our own js script in the pipeline flow, and used java collections in it.
can this lead to memory leak. as I believe there must be some GC activity taken place by snaplogic jvm itself. do we have to care about the variables that we declare in our javascripts ?
we are facing same memory leak issue, even after finishing pipeline execution the memory is not getting freed.
as you said it is unusual so does that mean our custom javascript code is leaking memory and if that is the case the variables memory clean up task should be performed by snaplogic itself.
Regards,
Aditya Kurhade.

0 Kudos