Explicit graceful shutdown for Spofire Server
You can manually stop Spotfire Server instances in a manner that controls the minimum draining and the draining timeout when the server needs to be restarted due to configuration changes.
When Spotfire Server has a configuration change, a software upgrade, or a change made to a schema that requires restarting, then you can explicitly shut down the server gracefully, controlling the following aspects of the shutdown, and informing the back-end services that the server instance is offline and should not be used for new requests.
graceful-shutdown
accepts two values.
Setting | Description |
---|---|
minimum-draining-seconds
|
Specifies the minimum amount of time that the command waits before it returns. |
draining-timeout-seconds
|
Specifies the maximum time that the command waits for the instance becoming idle. It must accommodate the longest operation (for example, an information services query or a save to library operation). |
graceful-shutdown --minimum-draining-seconds=2000 --draining-timeout-seconds=3600
If you do not explicitly call
graceful-shutdown
, and the server detects a
configuration change that requires a restart, then the server stops. For
information about configuring the server or the server cluster to always manage
automatic shutdowns gracefully, see
Graceful shutdown configuration settings.
- Enabling a graceful shutdown of a single Spotfire Server instance
Upgrading or changing the configuration of Spotfire can cause the server to stop and then need to be restarted to include the change. You can configure the server to shut down gracefully automatically. - Enabling a graceful shutdown of a Spotfire Server cluster
Upgrading or changing the configuration of Spotfire can cause the server cluster to stop and then need to be restarted. You can configure the server cluster to restart gracefully automatically.