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.
... View more
