Graceful Death for NodeBooter

[tuan]

Right now, in order to terminate NodeBooter?, Ctrl-C or kill is used. Other processes are still in the memory after NodeBooter? is killed.

[balister]

My recollection of the problem is that Control-C provides a (relatively) clean exit for the system and cleans up all components.

The problem is when something abnormal happens, then you are left with stuck processes that you need to kill -9.

I'd suggest running some actual tests to work out the exact problem, before wading into the code.

I think there is a method, maybe releaseObject, you can call on the Domain Manager to initiate a system shutdown, but this may turn into a lot of work, with numerous backward compatibility issues.

[shereef]

As of 0.8.1, nodeBooter attempts to properly shutdown the system, but the shutdown will fail in most circumstances. There is only one test case that I have been able to achieve "proper" system shutdown. The reason for failure to shutdown resides in our misuse of CORBA that leads to "memory leaks" within the ORB. In other words, not all CORBA instances can be properly terminated. Also, child processes seem to stop responding at shutdown, so the parent process forces a "kill", most of the time. If the system experiences a run-time error, then the child process may or may not be killed, depending on the error. The current nodeBooter provides a mechanism that could lead to proper shutdown of the system, but the core needs to be rigorously reviewed and modified to achieve a true system shutdown.

[cdietric]

Milestone Release 0.8.2 deleted