Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe what happens when a 'conduct stop' command is issued. #362

Open
longmuir opened this issue Apr 25, 2017 · 0 comments
Open

Describe what happens when a 'conduct stop' command is issued. #362

longmuir opened this issue Apr 25, 2017 · 0 comments

Comments

@longmuir
Copy link
Contributor

These page could use more information about what happens when a bundle is stopped.
https://conductr.lightbend.com/docs/2.1.x/DeployingBundlesOps
https://conductr.lightbend.com/docs/2.1.x/DeployingBundles

An example command of stopping a bundle would be helpful, with an explanation of how the application is stopped. I believe a SIGTERM is issued to the application, and it is provided with a configurable amount of time to perform a graceful shut down, but this should be documented more clearly.

More to the use case, graceful shutdowns are a very common question we receive from customers and this is one piece of that puzzle. As Akka is the most common type of application we've seen for ConductR, it may even be worth pointing out that this would automatically trigger Akka's co-ordinated shutdown feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant