topic Re: SAS/CONNECT and Grid in Administration and Deployment

SAS/CONNECT and Grid

woo — Mon, 11 Mar 2024 07:31:04 GMT

Hello friends,
I have dumb question may be. We are running with sas 9.4 m7 on linux and it's a grid environment. I don't know why but I do not see SAS/CONNECT is up and running on any grid node or don't see plug-in for SMC as well. What I am missing here? Of-course base sas and sas/connect is required on each node not I don't see it either in services as well.
Thank you

Re: SAS/CONNECT

Tom — Sat, 09 Mar 2024 01:06:00 GMT

I don't think SAS/Connect is needed for a GRID environment. The GRID tools will take care of running the SAS processes on the right node.

To see if it is licensed run PROC SETINIT.

To see if it is installed run PROC PRODUCT_STATUS.

Re: SAS/CONNECT

AhmedAl_Attar — Sat, 09 Mar 2024 01:36:01 GMT

Hi @woo

Check these links

SAS Help Center: SAS Grid Topology

https://support.sas.com/publishing/pubcat/chaps/61471.pdf

They have SAS Grid Topology diagrams

Re: SAS/CONNECT

LinusH — Mon, 11 Mar 2024 07:16:12 GMT

SAS Grid comes in threes different flavours, SAS Grid manager, Platform and Hadoop.

The first one requires SAS/CONNECT on all involved servers, but I think the control node not necessarily needs to have the SAS/CONNECT Spawner service running...?.

Re: SAS/CONNECT

JosvanderVelden — Mon, 11 Mar 2024 10:44:32 GMT

Like Tom mentioned you can check the licensed and installed products by using the setinit and product_status procedures. And if you have access to the softwaredepot used for the installation you can check the license-file in the softwaredepot itself. It should have SAS/Connect.

Re: SAS/CONNECT and Grid

doug_sas — Mon, 11 Mar 2024 12:08:35 GMT

SAS/CONNECT is a pre-requisite for any grid product so you should have it licensed, but unless your plan file specified CONNECT spawners to be running, they will not automatically be set configured by SDW.

SAS Grid can start CONNECT servers by adding the grdsvc_enable statement before the SIGNON statement so a spawner is not needed. CONNECT servers started this way are often called 'grid servers', but are just CONNECT servers started by the grid provider (SWO, LSF, YARN).

Re: SAS/CONNECT

woo — Mon, 11 Mar 2024 12:14:11 GMT

Thank you Tom/Everyone for comment.

Both, proc setinit; and proc product_status on node shows 'SAS/CONNECT - custom version information: 9.4_M7'.

Re: SAS/CONNECT and Grid

woo — Mon, 11 Mar 2024 16:12:47 GMT

Thank you Dog for your comment. I do see SAS/CONNECT in proc setinit and proc product_status though.

So this way from your comment "CONNECT servers started this way are often called 'grid servers', but are just CONNECT servers started by the grid provider (SWO, LSF, YARN)." ---- is this means, they have node configured and that is why it plug-in doesn't exist in SMC? When Grid starts connect server, any way to track it?

Re: SAS/CONNECT and Grid

doug_sas — Mon, 11 Mar 2024 16:19:17 GMT

You track things started on the grid through the Grid provider's UI.

SAS Workload Orchestrator serves up its own UI (no mid-tier needed)
SAS has the SAS Grid Manager Module for SAS Environment Manager to serve up one for LSF (mid-tier required).
Hadoop YARN has the UI for the YARN Resource Manager

Re: SAS/CONNECT and Grid

woo — Mon, 11 Mar 2024 17:48:06 GMT

Thank you.

We are running with LSF and gsub. We don't have grid orchestrator.

Any commands we can use? ps -ef cmd doesn't shows any process with connect spawner. We have multiple sasapp and for same app servers, we have obj. spawner definition defined.

Re: SAS/CONNECT and Grid

SASKiwi — Mon, 11 Mar 2024 19:12:34 GMT

Have a look in SAS Management Console. If SAS/CONNECT is installed then I'd expect to see this on all App nodes:

Re: SAS/CONNECT and Grid

gwootton — Mon, 11 Mar 2024 19:28:29 GMT

With a grid configuration you would not need to have a SAS/Connect Spawner and Server configured, this would be an optionally configured component and in your case it sounds like one has not been configured.

Instead, you would use GRDSVC_ENABLE to launch a connect server as a grid job directly rather than submitting a request to launch a connect server to the connect spawner, which would not make use of grid.

Re: SAS/CONNECT and Grid

doug_sas — Mon, 11 Mar 2024 19:48:16 GMT

It is more accurate to say 'if SAS/CONNECT is configured' instead of installed. SAS/CONNECT can be installed, but if you did not have any SAS/CONNECT Server Configurations (or SAS/CONNECT configurations) defined in your plan file, a SAS/CONNECT spawner would not have been configured and Logical CONNECT servers may not have been configured either.

Re: SAS/CONNECT and Grid

doug_sas — Mon, 11 Mar 2024 19:53:55 GMT

@woo wrote:

Thank you.

We are running with LSF and gsub. We don't have grid orchestrator.

Any commands we can use? ps -ef cmd doesn't shows any process with connect spawner. We have multiple sasapp and for same app servers, we have obj. spawner definition defined.

A spawner is not needed in a grid. LSF replaces the spawner as the daemon that starts CONNECT servers. Run the following code:

%put rc=%sysfunc(grdsvc_enable(_ALL_,server=SASApp));
SIGNON T1;

(this assumes you have a SAS Application Server context 'SASApp' that has a logical grid server defined)

Once this runs, there should be a SAS process running on the grid in CONNECT server mode. Use the LSF 'bjobs' command from a terminal to see the job information. To make the server go away, run the following code:

SIGNOFF T1;

If you had a CONNECT spawner, the process name would be 'cntspawn' in 9.4