topic Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03 in Administration and Deployment

Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

ravikumar901 — Wed, 20 Nov 2024 13:33:47 GMT

Hi All,

Im facing frequently session resetting issue in SAS Studio in Viya 4. I couldnt able find anything in compute service pods and compute server pod . Please help me out. Thanks in advance.

Regards,
Ravi

Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

Sajid01 — Wed, 20 Nov 2024 23:02:46 GMT

Hello
The compute server log can give an idea of whats going on. Ask the SAS Admin to look into it.
Secondly do create a support ticket with SAS Tech Support.

Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

ahmedaldorr — Tue, 03 Dec 2024 11:55:20 GMT

hello, I wonder if you got this issue resolved, as I have the same issue

Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

Kurt_Bremser — Tue, 03 Dec 2024 12:00:11 GMT

Same answer: open a ticket with SAS technical support. Or have your local SAS admin do it.

Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

sasefj — Wed, 04 Dec 2024 17:51:24 GMT

Again, please get in touch with Tech Support about your issue. But in the meantime, it might be helpful to try increasing the memory limits for the sas.launcher.max and sas.launcher.default configurations in SAS Environment Manager to 8Gi. It's hard to say whether this adjustment will help with your situation.

Re: Compute session resetting while working SAS Studio in SAS Viya 4 lts 2024.03

JasonTran910 — Tue, 24 Dec 2024 16:12:22 GMT

This can be caused by a variety of issues, but resources limitations usually being the common cause such as running out of storage in SASWORK or overreaching the memory limits for the sas-programming-environments container in the sas-compute-server pod. I would recommend to configure external strorage for SASWORK as described in the documentation so that the ephemeral storage on the compute node is not being utilized (emptyDir). You might want to check the describe of your compute node to ensure that the node is not having any disk pressure when this issue occurs.:

Configure External Storage Class
https://go.documentation.sas.com/doc/cn/sasadmincdc/v_059/calsrvpgm/n0k315nlna2awln119phkhua1na2.htm

And/or increase the launcher memory limits:

Manage Requests and Limits for CPU and Memory
https://go.documentation.sas.com/doc/ja/itopscdc/v_058/itopssrv/p0wvl5nf1lvyzfn16pqdgf9tybuo.htm#n0u9kbsqdgyoean1ofbds3oe4wq5

If your program or job causes the sas-programming-environments container to exceed the memory limits (default is 2Gi) then kubernetes will terminate the sas-compute-server pod which you would then see the warning message in SAS Studio Viya stating that your session has encountered a problem and prompting you to reset the session. I would recommend testing with setting the launcher memory limits to something like 8Gi to see how things behave.