[ https://forge.continuent.org/jira/browse/SEQUOIA-961?page=comments#action_14045 ]
Robert Hodges commented on SEQUOIA-961: --------------------------------------- For now I would vote to make this configurable and off by default. This is probably the best in my opinion. We are thinking about how to manage start/stop operations in general. Another option which seems to be quite attractive is to implement start/stop using the Java Service Wrapper. The idea behind the shutdown hook is a good one--prevent unfortunate accidents especially if someone shuts down the system without thought. > PATCH: Support for controller "safe shutdown" via > Runtime.getRuntime().addShutdownHook() > ---------------------------------------------------------------------------------------- > > Key: SEQUOIA-961 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-961 > Project: Sequoia > Type: Improvement > Components: Core > Versions: Sequoia 3.0 beta3, Sequoia 3.0 beta2 > Reporter: Landon Fuller > Assignee: Damian Arregui > Priority: Minor > Fix For: sequoia 2.10.10 > Attachments: patch-SIGINT > > Original Estimate: 0 minutes > Remaining: 0 minutes > > To support safe administrator shutdown of Sequoia via the use of signals (eg, > SIGINT via a FreeBSD rc.d init script), I added a simple Java shutdown hook > that: > 1) Shuts down all virtual databases using SHUTDOWN_SAFE > 2) Calls controller.shutdown() > This ensures that the controller can (almost) always be shut down cleanly, > even in the administrative console is not available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
