Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.
There are multiple ways to undeploy a pu. For example, it can be done from the command line, web ui or in your case using the Admin API. In the end, they are calling the Admin API internally to do the undeployment. So the choice of your tool depends on what suits you. You don't mention why it was unsuccessful.
Hi Dixson,
To clarify, on calling undeploy(), the Mirror Service PU was removed from Gigaspaces Web UI however the related process was not killed using 'ps -ef' to search for the process id on the node. We noticed that there was a memory shortage error before we undeployed so it may be related?
With previous testing, we noticed that if the Mirror Service PU is INTACT, then usually undeploying it kills the associated process id. However, when the Mirror Service PU is BROKEN, the associated process id is still running when we try to undeploy it.
Perhaps we can kill the GSC itself after the PU undeploy to ensure that the PU resources have been freed up?
Perhaps it is possible to get the process id for the pu and then kill it?
Thanks, KP
If you are using the service grid, then deploying the GSC and the processing unit are 2 distinct steps and these components are managed separately. If you undeploy a processing unit it won't kill the GSC it was running in.
See: https://docs.gigaspaces.com/xap/12.3/... and https://docs.gigaspaces.com/xap/12.3/...
Run kill from the command line, if you're intention is to make the gsa automatically start another one. Otherwise you can do a shutdown, but you would have to start another one.
Asked: 2018-06-15 09:47:33 -0500
Seen: 395 times
Last updated: Jun 15 '18
Copyright GigaSpaces, Inc. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
