Qlik Community

New to Qlik Sense

If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.

Announcements
Read about the latest Qlik Community enhancements on the Community News blog!
cancel
Showing results for 
Search instead for 
Did you mean: 
JacobT
Partner
Partner

QliKSense November 2020 Memory Leak?

Hi!

One of our customers are running QlikSense November 2020 release.

From Junary there has been problems with the services for QlikSense where they enter a stall state,
they crash but are still in the state of running. Because of the way this happens it won't log it in QlikSense logs.

They use another company that maintain the infrastructure and they set the Windows Application logs to 32mb, which is only 2 weeks back and the log for the days when we had the problems is not there.

What happens around the time this started was the developers starting developing and testing i production which put more preassure on the servers.

Memory is ~70% used in average with no peak over 75%
CPu is  ~95% used in average.

Memory leakage or what would the guess be on the problem?

Anyone else had similar problems with this version?

1 Solution

Accepted Solutions
JacobT
Partner
Partner
Author

We havn't had the problem again so far, but expanded the logging capabiltiies for when it happens the next time. Closing the thread for now.

View solution in original post

3 Replies
JustinDallas
Specialist II
Specialist II

Might be related, but this morning I had my central node just outright die on me this morning.  The Windows OS was up an chugging along, but all the services had stopped.  I've never seen that happen before, and the EventViewer looked relatively clean.  I'm going to look at my other logs later today.

JacobT
Partner
Partner
Author

Similar but not exactly the same, our services don't go into stopped, they just act like it.

JacobT
Partner
Partner
Author

We havn't had the problem again so far, but expanded the logging capabiltiies for when it happens the next time. Closing the thread for now.

View solution in original post