Replies: 1 comment 1 reply
-
Hey, yes, I can help with this. Actually, this would be an enhancement request, which would be good to be an Issue. Do you mind changing it to an Issue, or opening it as one? There's a choice to 'reference in new issue' but I think if I click that I'll be the one opening the issue. The IOM access method uses Java since there's no Python IOM client, so I use the Java IOM client and have an interface between Python and Java to do that. So, the subprocess in this case is the Java process. IOM is an asynchronous interface, so it seems like I may need to be doing something extra that I'm not, to terminate the SAS side, when you terminate the Python side abnormally. I have an idea but need to investigate. Thanks, |
Beta Was this translation helpful? Give feedback.
-
I am using winiom configuration , from a remote machine to our sas server. I happen to be using this with dagster if you're curious.
My scenario is in the case where the job is kicked off, I want to be able to cancel it from the remote machine, rather than tracking it down in the SAS server.
My code looks like this :
When I kill the running job I get the following in my stdout, which is what I expect:
In this specific test case above i got the SAS process id from the session object :
When I logged into the SAS server to see if it was really ended, I see that it is in fact still running, and I must manually end it from there.
Whats the difference between the subprocess id from the stdout and the SAS process id property of the sassession?
How can i be sure that the process is cleaned up properly in this scenario?
I hope this question is useful to the community!
Beta Was this translation helpful? Give feedback.
All reactions