11-20-2017 04:04 AM - edited 11-21-2017 01:48 AM
I have SAS 9.4 grid implemented on a linux environment.
Recently there have been lot of issues with CPU usage in SAS.
Today i tried to trace this and found that the object spawner process is consuming a lot of CPU.
Does anyone knows why this could be happening ?
And how can this be controlled ?
I have attached a document showing details of my findings.
Thanks in advance !!
11-20-2017 04:27 AM
You can do yourself a favor by posting such documents (where more than simple text is needed) in pdf format. Downloading a .docx could get me fired if it contained malware.
11-21-2017 01:59 AM
Have you already stopped and restarted the object spawner to see if it goes again to the same state? If yes, open a track with SAS technical support. I can't remember if I ever had a spawner misbehave like that (I had hung spawners in the past, but they were simply doing nothing, and restarting fixed it).
11-21-2017 02:12 AM
Restarting does fix it.
But it started behaving the same way again.
How long does it take until it starts over-using CPU? For some processes, I have a regime of nightly restarts.
11-21-2017 02:59 AM
If your problem usually appears after more than a day has passed, then (as a temporary remedy) I would advise to configure a restart of the spawner via crontab, sometime in the night. But I'd still open a track with SAS TS, as this is not usual behaviour.
My spawner (AIX 7.1, SAS 9.4 TS1M2) has been running continuously since April 21, and consumed 1m50s of CPU in that time, which is negligible.
11-21-2017 02:10 AM
One thing that could be useful: look at the filesystem where the spawner (and maybe other SAS processes) write logs to. Sometimes they go into loops when they can't write to the log anymore.
(wants to write message, fails, wants to write error message, fails, wants to report that error, and so on ...)