03-14-2017 01:33 PM
There is a few days that we are having troubles with the LASR Servers of SAS Visual Analytics.
The problem is:
Lasr Servers Stopped:
LASR Analytic Server - MyServer
Public LASR Analytic Server - MyServer
LASR Server DBM
We could not find them yet. But there are somethings we've found:
I'd like to know what are the possible causes when the LASR Servers Stops.
And why these TKGrids processes are still running during days, even when we restart the sas.servers ?
Thanks in Advance
03-15-2017 01:01 AM
If your LASR Server(s) are stopped check the SAS Visual Analytics Administrator page where you can see their status. Right click then select LASR Action log to see if it has a recent log. You can also use this utilitity to monitor your LASR servers for things like table memory usage - Usage Note 58922: Using the LASRInfo.jar utility to see information about your SAS® LASR™ Analytic S... . If you have password-less ssh setup you can launch the TKGrid/bin/gridmon.sh script with X Windows running to see their memory usage, jobs, and activity. For more details see Paper 3275-2015 Great Performances: SAS® Visual Analytics Performance Monitoring and Enhancement.
The primary cause of LASR servers stopping, or at least not loading data is either you are out of memory on one of your node (80% of RAM usage), you reached a set limit of some sort such as ulimit number of files, number of processes, of ssh sessions. The second likely reason is communication failures between TKGrid nodes, SAS, and Hadoop cluster if you have it. The processes for a LASR server will continue to run as long as their is data loaded into LASR memory, which is why you see the memory continue to be used. The sas.servers does not start/stop LASR servers, you typically do this from SAS Visual Analytics Administrator, or autoload can possible start them automatically if configured.