Skip to main content

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

cancel
Showing results for 
Search instead for 
Did you mean: 
gandalfgray
Specialist II
Specialist II

Very high cpu usage in Central Node repository service

We are on Qs Nov 2019 patch 3

Sometimes the repository service at our central node starts running at 90-100% cpu usage for a period.

When this happens the QMC becomes unresponsive.

If we are lucky, the CPU usage goes down after 10-20 minutes, but sometimes we have to kill and restart the service.

 

Does anyone knows what can cause this?

We tried to find something in the logs, but haven't seen anything specific for these periods.

1 Solution

Accepted Solutions
gandalfgray
Specialist II
Specialist II
Author

We found what's probably the cause and a solution.

See https://support.qlik.com/articles/000059664

View solution in original post

4 Replies
gandalfgray
Specialist II
Specialist II
Author

We found what's probably the cause and a solution.

See https://support.qlik.com/articles/000059664

vitaliichupryna
Creator III
Creator III

Hi! Have you seen any negative effects on the server after implementation?

Regards,

Vitalii

gandalfgray
Specialist II
Specialist II
Author

Hi Vitalii

Well, we did not see any effect, negative or positive.

 

But, we have recently done a couple of things which both seems to have a positive effect:

  • 2 months ago we upgraded to Jun 2020 patch 4, and that stopped the constant build up we had using the Nov 2019 p3 version. But we still had a increase of cpu% baseline each 21th day roughly (why??)
  • 10 days ago we upgraded to a larger/faster database server for the Sense repo db, and at the same time migrated to 9.6.19 of postgresql (think we had 9.6.6 or something like that before). This lowered the Repository services cpu consumption even more. It will be interesting to see if we still get the 21th day increase...

See the screenshot, it shows a clear problem with the Nov 2019 setup we have had most of this year (we upgrade to Nov 2019 in February, and did not have the problem before as can be seen)

 

 

vitaliichupryna
Creator III
Creator III

Hi Gandalfgray!

Thank you for your answer, as I see from your chart, you got a CPU issue after upgrading to Nov 2019 in March 2020. Is it correct?

Thanks,

Vitalii